From: Michael Stevens (Michael.Stevens_at_[hidden])
Date: 2004-07-29 09:03:19
BBv2 read your own user-config.jam from you home directory. How this works is
in the documentation. Seach boost_build_v2.html for site_config.jam and
I recall last month (or a couple of months back) the ALL_LOCATE_TARGET issue
was mentioned in this mailing list. I think the current BBv2 status is that
it doesn't support it directly. However this does not mean you cannot role
You can use the 'build-dir' parameter of the 'project' rule to override the
default build dir. If you need a global way to do this you could set an
variable and use this instead of specifying a literal path as the argument.
Two good places to set such a variable are in your user-config.jam or in your
boost-build.jam. The later is more powerful as it searched in the filesystem
heirarchically and can therefore be easily customised
> I cannot find such a way in v2's docs for the dynamic definition of
> toolset and binaries destination. Also, when I use "bjam toolset=gcc" I
> get a " warning: no toolsets are configured" message.
I think this just mean you haven't yet defined any toolset. This should be
done in the user or site config.
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