|
Boost-Build : |
From: David Abrahams (dave_at_[hidden])
Date: 2002-09-10 08:43:33
From: "Vladimir Prus" <ghost_at_[hidden]>
> > Not everything can be built either static or shared. For example, see
the
> > threading library. Also see Boost.Python v2: you can build a static
> > library, but it might only make sense if you're going to do embedding
(not
> > extending).
>
> You can do this with requirements.
>
> > It's easy enough to make a single rule which does both/either if you
have
> > separate rules, but can we go the other way if you collapse them into
one?
>
> I don't see a problem.
OK.
> > Also, is this really worth spending cycles on at this point?
>
> If Milestone2 is going to build Boost with gcc, we'd need to build
> libraries also. We can agree to use separate rules for now, and revisit
> this topic later, however.
If it's just as easy either way, then by all means, try it your way first.
-----------------------------------------------------------
David Abrahams * Boost Consulting
dave_at_[hidden] * http://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