$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: David Abrahams (dave_at_[hidden])
Date: 2005-07-04 12:12:53
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
sense?
> The right solution is a combination of:
>
> 1. <use>-in only the needed 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.
Maybe; I still have a hard time understanding that using a project
means using every library in it.
-- Dave Abrahams Boost Consulting www.boost-consulting.com