Boost logo

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
> > 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
> > extending).
> You can do this with requirements.
> > It's easy enough to make a single rule which does both/either if you
> > separate rules, but can we go the other way if you collapse them into
> I don't see a problem.


> > 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] *


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at