Subject: Re: [Boost-build] Projects requirements and alternative selection
From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2009-04-16 05:06:37
Vladimir Prus wrote:
> On Wednesday 15 April 2009 16:38:28 Johan Nilsson wrote:
>> I'm experiencing some "problems" with target selection. A simplified
>> Is this as expected - I had a gut feeling that the requirements set
>> by "project" should be added to the "build" request for the bar lib
>> in the above scenario?
>> I've tried the above using Boost.Build from trunk as well as from
>> 1.34.1. Toolset is msvc (set in user-config.jam).
> You are hitting:
> I'd recommend that instead of alternatives, you use one target with
> indirect conditional requirements that computes <file> property as
Is that the recommended long-term approach as well? Seems a bit awkward to
Would it be possible for you to describe a bit more in detail what
happens/should happen in the actual implementation and also list a couple of
possible approaches to fix this? I could take a look at it.
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