From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-04-26 01:35:39
Vladimir Prus wrote:
> On Monday 25 April 2005 19:35, Rene Rivera wrote:
>>This is something
>>that lib authors added to BBv1 as a user convenience.
>>So that they could
>>cd libs/whatever/build, and build only that library but still have it
>>someplace convenient instead of in the variant subdirs (bin.v2/..).
> Hmm... why is that? For testing, this is not needed. And for building Boost,
> top-level Jamfile is fine. You know, I doubt that every library author
> intentionally added the 'stage' declaration, they most probably just copied
> some other Jamfile and modified library name and source names, so we should
> not assume all library authors want this behaviour.
I wasn't assuming that in this case :-) -- We've had questions from
users about why doing bjam in a libs build directory didn't build the
targets any place useful. And also had user questions about the top
level install options and targets not working in the lib/*/build
subdirs. So this is something people want.. Don't know how to provide it
with the current architecture in a consistent way though. Any ideas
on how to provide a "global" build/install interface?
By the way feel free to remove them ;-) -- Except for the ones in
tools/Jamfile.v2. I'm using those for building the tools someplace I can
grab them easily for the Windows installer I posted about elsewhere.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
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