From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-04-26 02:18:52
On Tuesday 26 April 2005 10:35, Rene Rivera wrote:
> 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?
Basically, we need 'install' and 'stage' work in any lib subdir? And also
recognize --prefix and --layout. What about --with-* options, should they be
I suppose I can use some tricks like making top-level Jamfile declaring
necessary targets in librarie's Jamfile.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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