Subject: Re: [Boost-build] Unused propagated features and build directories
From: Vladimir Prus (ghost_at_[hidden])
Date: 2010-11-06 11:39:16
On Saturday, November 06, 2010 02:00:44 ÐÐ»ÐµÐºÑÐµÐ¹ ÐÐ¸ÐºÐ¸ÑÐ¸Ð½ wrote:
> In next small example on build exe e1 and e2 library l1 build twice
> (in path with and without "/f-on/") although it is not necessary.
> feature.feature f : on : composite propagated optional ;
> feature.compose <f>on : <define>F ;
> lib l1 : l1.cpp ; # don`t use define F
> lib l2 : l2.cpp l1 ; # use define F
> exe e1 : e1.cpp l2 ;
> exe e2 : e2.cpp l2 : <f>on ;
> It is possible change example so that may to build l1 in own directory
> (when build e1 and e2)?
You can add <f>off as requirement on l1. While there are cases when
Boost.Build could automatically detect that a feature is not relevant,
this appears the case where manual specification will always be required.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build: http://boost.org/boost-build2
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