From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-04-05 03:48:15
Zbynek Winkler wrote:
> The algorithm was said to handle <toolset>msvc-6.0 instead of
> <toolset-msvc:version>6.0 so I tried
It turns out that this is not yet supported for alternative selection. I'm
thinking what can be done.
> lib cppunit : : <name>cppunitd60 <variant>debug <threading>multi
> <toolset>msvc-6.0 <search>d:/software/cppunit-1.8.0/lib ;
> but that did not work. For some (to me unknown) reason bjam tried to
> link against cppunit71.lib so I've got bunch of unresolved referencies.
> I use msvc-6.0 as my default toolset so I tried compiling with msvc-7.1
> by issueing 'bjam toolset=msvc-7.1' and this is what I've got:
> d:/software/boost-build-cvs/v2/build\feature.jam:680: in
> expand-composites from module feature
> error: explicitly-specified values of non-free feature
> <toolset-msvc:version> conflict
> existing values: 7.1 6.0
Yes, this reproduces for me as well.
> I give up.
I think the fix I've comitted should allows you to still use
<toolset-msvc:version>XXX as condition. Meanwhile, I'll look about fixing
other cases, though as usual, this might take some time.
> PS. I suggest adding some unit test for this so we do not get such
> reggressions in the future.
Definitely. As soon as I have a solution I'll write some tests.
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