Subject: Re: [Boost-build] project requirements in Jamroot --- how to make sure they propagate to sub-projects and other dependencies
From: Konstantin Litvinenko (to.darkangel_at_[hidden])
Date: 2009-01-11 04:14:25
Thorsten Ottosen Ð¿Ð¸ÑÐµÑ:
> Steven Watanabe skrev:
>> Thorsten Ottosen wrote:
>>> I thought everything I specified in my Jamroot file would propagate
>>> to both sub-projects and dependencies in Boost. I know _SECURE_SCL=0
>>> is the
>>> problem here since uncommenting it makes everything work again.
>>> Am I doing something wrong?
>> <define> is used for all subprojects, but is not propagated to
>> Off the top of my head, I don't have a good solution.
> Ok. But there are a number of macros like this in boost that needs to be
> consistently defined over both boost libs and others. BOOST_NO_EXCEPTION
> would be one example.
> I guess I can go to libs/test/build/ and say bjam
> --define="_SECURE_SCL=0", although that is somewhat annoying.
> Does anybody have a better idea?
Define composite feature:
feature.feature secure-stl : on off : propagated composite optional ;
feature.compose <secure-stl>off : <define>_SECURE_SCL=0 ;
and than use it:
exe test : main.cpp lib1 : <secure-stl>off ;
it will be applied to lib1 and all its dependencies.
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