From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-01-03 12:27:25
On 2002-01-02 at 10:20 AM, david.abrahams_at_[hidden] (David Abrahams) wrote:
>----- Original Message -----
>From: "Rene Rivera" <grafik666_at_[hidden]>
>> >The globbing would require another extension to the core Jam source.
>> >you like to volunteer?
>> Hmm, yes I think so. I'll take a look at the code and see. Espcially if it
>> increases the likelyhood of getting the crawl up the directories behaviour
>> implemented ;-) , which is rather more important to me.
>I don't want to discourage you from trying, but the upward crawl doesn't
>require any core Jam extensions.
OK, looking at some deatil last night I fail to see how it would not require a
The basic problem I ran into is that there is now way, that I can see, of
figuring out that one has crawled up past the top of the filesystem.
Am I missing something?
As a side note, I'm also seriously thinking of removing one of the limitations
that you've worked around... not being able to read the target spcific
attributes from "VAR on TARGET = X" assignments. Reading those values would
make doing this much cleaner as I could then tell what a "SEARCH on
somefile.jam = PATHS" found without having to blindly call "include" and
generating a "perror" if there was nothing found.
For this I was thinking of syntax like so: "$(targetvaraible:V=hashvariable)".
So for SEARCH it would something like: "$(SOMEFILE:V=SEARCH)" which would
evaluate to either the file it found, or null if not found. For non
SEARCH/LOCATE it would just evaluate to the previously set value, or null if
-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk