From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-08-16 01:03:41
On Sunday 14 August 2005 23:41, David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> > Hi,
> > I've a use case which is not very well supported by V2 at the moment:
> > project
> > : requirements
> > : <library>/some_library_that_takes_long_time_to_build ;
> > lib runtime1 : main1.cpp common ;
> > lib runtime2 : main2.cpp common ;
> > lib common : common.cpp : <link>static ;
> > So, I have some library "common" that I made static to avoid the trouble
> > of installing yet another library. However, that library gets project
> > requirements too, and so tries to build
> > some_library_that_takes_long_time_to_build with <link>static. Now, I
> > don't want that at all, not to mention that static library can't be
> > linked with another static library.
> > However, there's no easy way to avoid this behaviour.
> How about just having BBv2 ignore requirements like that one that
> aren't relevant to the target?
How are they not relevant? <link>clearly affects how libraries are built...
and generally affects also object files (-fPIC flag is added on Unix for
-- 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