Fix separate compilation in CI

`optional` adds a "null" default feature value, effectively defaulting
to `off`, instead of `on`.

Signed-off-by: Damian Jarek <damian.jarek93@gmail.com>
This commit is contained in:
Damian Jarek
2019-05-31 01:57:02 +02:00
parent 52668cf730
commit ad66be6eb7
2 changed files with 8 additions and 2 deletions

View File

@ -1,3 +1,9 @@
Version 258:
* Fix separate compilation in CI
--------------------------------------------------------------------------------
Version 257:
* Add b2 features for compile-time options used in testing

View File

@ -31,10 +31,10 @@ lib crypt32 ;
lib ssl : : <target-os>windows <name>ssleay32 ;
lib crypto : : <target-os>windows <name>libeay32 ;
feature.feature boost.beast.allow-deprecated : on off : optional propagated composite ;
feature.feature boost.beast.allow-deprecated : on off : propagated composite ;
feature.compose <boost.beast.allow-deprecated>on : <define>BOOST_BEAST_ALLOW_DEPRECATED ;
feature.feature boost.beast.separate-compilation : on off : optional propagated composite ;
feature.feature boost.beast.separate-compilation : on off : propagated composite ;
feature.compose <boost.beast.separate-compilation>on : <define>BOOST_BEAST_SEPARATE_COMPILATION ;
variant beast_coverage