From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-03-25 12:06:49
----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>
> I've implemented part 1 of the new load behaviour.
Hooray for Rene!!!
> In particular the part that
> involves changing the Jambase. I've comiited the changes to the
Jambase in a
> "boost_build_v2" branch. Part 1 is the loading of the build system
> the loading of the Jamfile, etc. For now the check for the name of the
> executable succeeds when it has "bjam" in the name anywhere.
1. You're using tabs. The Perforce people have taken my suggestion it
appears; they have the removal of all tabs from the source on their TODO
2. I'm a little uncomfortable with glob-to-root used to search from a
directory to the root, because it will keep searching upward even after
the item is found. I know, I should not worry about this, but I keep
thinking about network file systems, etc...
3. What's the point of the gTARGET_LOCATION() pseudo-function variable
and the <bjam> grist? It's not obvious to me what you're trying to
I am trying to move away from pseudo-function variables, because all
those parens get hard to read:
I vote for a simpler syntax, like gTARGET_LOCATION.$(file)
> I'll get to the changes for the rest of the loading soon... not today,
> sometime this week.
> Could someone check to see if what I did works correctly on Windows.
> Particularly the path translation regarding "/".
How can we check? Do you have a test somewhere?
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