Re: [Boost-build] Using feature.compose with a toolset compiler version

Subject: Re: [Boost-build] Using feature.compose with a toolset compiler version
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-05-05 17:40:40

AMDG

On 05/05/2016 03:15 PM, Edward Diener wrote:
> <snip>
> So I change my feature lines to:
> 
> feature.subfeature toolset gcc : cpplevel : cxx11 : optional composite
> propagated ;
> feature.compose <toolset-gcc:cpplevel>cxx11 : <cxxflags>-std=c++11
> 

  This is the right way to do it, I think,
but it looks like composite subfeatures
are broken.  You're best bet is to make
it a top level feature instead of a
subfeature.

> and try again:
> 
> b2 toolset=gcc-5.3-cxx11
> 
> but I get:
> 
> notice: could not find main target cxx11
> notice: assuming it is a name of file to create.

  Now that is weird.  This is the error I would
expect if you put cxx11 by itself on the command
line.

> E:/Programming/VersionControl/modular-boost/tools/build/src/build\feature.jam:768:
> in expand-composites from module feature
> error: expansions of composite features result in conflicting values for
> error: values: xsltproc
> error: one contributing composite property was <toolset-gcc:cpplevel>cxx11
> 

  This is really a mess.  I'll see
what I can do, but I probably won't
get to it till after C++Now.

In Christ,
Steven Watanabe