From: Rene Rivera (grafik.list_at_[hidden])
Date: 2004-03-19 16:01:14
Graham Bennett wrote:
>>>I was wondering if there was any way to prevent Boost.Build from
>>>generating static libraries, as only require the shared libraries.
>>>I am using Boost 1.31.
>>Which Boost.Build? V1 or V2?
> V1, but if it is possible to move to V2 and it solves the problem I can
> use that.
There's no install support on V2 yet, so moving for that is not an option :-(
>>And do you mean making the build+install not generate the static
>>libraries? Or do you mean your own builds not generating static
> I meant the Boost build+install (I am building Boost, not my own
> project). I want to only generate libboost_*.so, not libboost_*.a.
Well the bad news is that there isn't a way to do that. This is because those
two are declared separetly, that is the static is one "lib" target, and the
dynamic is another "dll" target. They just happen to share the same name.
The situation is better in V2 as it uses a single target and produces
different version based on what you ask to build. But like I said no "install"
The best you could do is try and change the top level v2 build Jamfile to
produce a stage of the libraries you want.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
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