From b54d80c3e2c80f6a3d33aed5652616b3c405a3dc Mon Sep 17 00:00:00 2001 From: Vladimir Prus Date: Wed, 25 May 2005 13:51:33 +0000 Subject: [PATCH] Do no call sequence.unique on result of GLOB-RECURSIVELY. 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] --- v2/util/path.jam | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/v2/util/path.jam b/v2/util/path.jam index 781eb50fc..e9c234b1a 100644 --- a/v2/util/path.jam +++ b/v2/util/path.jam @@ -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) ] ] ; + }