From: David Abrahams (dave_at_[hidden])
Date: 2005-08-14 14:41:38
Vladimir Prus <ghost_at_[hidden]> writes:
> I've a use case which is not very well supported by V2 at the moment:
> : 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?
> Any comments or better ideas?
If you can't do the above, IMO the only clean solution is to move the
declaration of lib common out of that project.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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