boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-17 13:42:14 +00:00
Code Issues Projects Releases Wiki Activity

Do no call sequence.unique on result of GLOB-RECURSIVELY.

Browse Source 
That was an old hack which was only needed in one context -- when we
passed both Jamroot and jamroot as patterns, got back Jamroot and jamroot
(because windows is case-insensitive and reports that both exist), and get
confused.

Calling 'unique' does not harm in most cases, but in Boost Jamfiles we glob
for all headers, and O(n^2) algorithm used by unique considerably slows us.


[SVN r29187]
This commit is contained in:
Vladimir Prus
2005-05-25 13:51:33 +00:00
parent 7ef55e8276
commit b54d80c3e2
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
v2/util/path.jam
View File

@@ -214,11 +214,9 @@ rule glob ( dirs * : patterns + )
}
}
# Windows is not case-sensitive, so if you're globbing
# for Jamroot and jamroot, the result will include 'Jamroot'
# twice. Remove duplicates.
return [ sequence.unique [ sequence.transform path.make :
[ GLOB-RECURSIVELY $(real-patterns) ] ] ] ;
return [ sequence.transform path.make :
[ GLOB-RECURSIVELY $(real-patterns) ] ] ;
}