From: Jürgen Hunold (hunold_at_[hidden])
Date: 2005-07-05 01:40:32
On Maandag 04 Juli 2005 19:12, David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> > I think the situation is that Jurgen has <use>/boost
> > somewhere. That, in turns builds every single target in Boost, and
> > propagates usages requirements back to the dependent. Including that
> > <async-exceptions> thing.
> Why is that an appropriate behavior? For what use case would it make
Yes, this is the question our discussion boiled down to.
> > The right solution is a combination of:
> > 1. <use>-in only the needed libraries
Well, I normally use only header-only libraries.
> > 2. Add "alias headers ; " to top-level Boost Jamfile.v2, and
> > <use>/boost//headers. This way, you'll get <include> usage requirements
> > from top-level Jamfile.v2, and nothing else.
This would be great.
> Maybe; I still have a hard time understanding that using a project
> means using every library in it.
Yes. Especially since the new alias "headers ;" would be subject to this
behaviour, too. In this case this is good but it might be better to
explicitly put "headers" in the usage-requierements of "project /boost ;"
-- * Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau * voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover * fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover * hunold_at_[hidden] ! www.ive.uni-hannover.de
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