|
Boost-Build : |
From: Jurko Gospodnetiæ (jurko.gospodnetic_at_[hidden])
Date: 2007-12-21 12:28:27
Hi.
I'm using Boost Build milestone 12 and I just discovered that
conditional features conditioned on a toolset version and another
feaeture do not work.
Below are the examples tested with MSVC toolset, version 7.1. and
using features <toolset> and <variant>. We also ran similar tests using
MSVC 8.0 and all gave exactly the same results.
------------------
Tests that failed.
------------------
Example 1.
----------
Compiler option applied on msvc-7.1, debug and release builds but
should be applied only on debug builds. Does not matter whether we
specify --toolset=msvc or --toolset=msvc-7.1 on the command line.
<toolset>msvc-7.1,<variant>debug:<cxxflags>/buga-wuga
Example 2.
----------
Compiler option applied on msvc-7.1, debug and release builds but
should be applied only on release builds. Does not matter whether we
specify --toolset=msvc or --toolset=msvc-7.1 on the command line.
<toolset>msvc-7.1,<variant>release:<cxxflags>/buga-wuga
-------------------
Testes that passed.
-------------------
Example 3:
----------
Compiler option not applied on msvc-7.1, debug or release build.
<toolset>unga-bunga:<cxxflags>/buga-wuga
Example 4:
----------
Compiler option applied on msvc-7.1, debug and release build.
<toolset>msvc:<cxxflags>/buga-wuga
Example 5:
----------
Compiler option applied on msvc-7.1, debug and release build.
<toolset>msvc-7.1:<cxxflags>/buga-wuga
Example 6:
----------
Compiler option applied on msvc-7.1, debug build but not applied on
msvc-7.1, release build.
<toolset>msvc,<variant>debug:<cxxflags>/buga-wuga
Example 7:
----------
Compiler option not applied on msvc-7.1, debug build but applied on
msvc-7.1, release build.
<toolset>msvc,<variant>release:<cxxflags>/buga-wuga
Example 8:
----------
Correctly recognizes <buhaha> as an unknown feature.
<toolset>msvc-7.1,<buhaha>shreek:<cxxflags>/buga-wuga
We really need this feature as one of our project whose build is
implemented using Boost Build is growing and getting ported to different
OSs/compilers. If this is a bug and not something we misunderstood, is
there any chance of it getting fixed for the upcoming Boost 1.35 release?
Best regards,
Jurko Gospodnetiæ
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