Subject: Re: [Boost-build] Packaging features together
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-10-08 14:42:17
On 10/08/2013 08:06 AM, Michael Price wrote:
> What I would like to do is to take all of the features that are required
> for all of my projects and package them together so that the author of a
> particular jamfile doesn't have to know all the details of the features
> being used.
> It looks like defining my own composite feature might be the right
> solution, but this feature will only ever have a single value (i.e. "on").
> Is it possible to make it so that a value for the feature doesn't/cannot
> be specified?
No. I usually use "on" for things like this.
> Another problem I think would be how to get that composite feature defined
> in a central file and then available to all of the other projects. Is this
> something I would use a custom module for? If so, what would that even
> look like.
project requirements are inherited, so if
your projects are all in the same tree, you
can just put this in your Jamroot:
project : requirements <foo>bar ... ;
> Sorry if these are n00b questions, but we are trying to get a large
> codebase building with Boost.Build and we are just getting started with it.
> Thanks to anyone for any helpful suggestions.
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