From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2006-03-31 13:58:07
Attached is a test case that demonstrates my problem.
You were right that in the simplest case it works. It worked fine with empty
jamroot, but then I added a project in it to specify static linking by
default, and this triggered the problem. So, in the attached jamroot, if you
comment out the line that says "<link>static", it will all work.
I am not sure if this is by design or if it is a legitimate bug. If it isn't
a bug, can someone please explain the logic behind this behavior?
----- Original Message -----
From: "Vladimir Prus" <ghost_at_[hidden]>
To: "Boost.Build developer's and user's list" <boost-build_at_[hidden]>
Sent: Friday, March 31, 2006 5:41 AM
Subject: Re: [Boost-build] Selecting different sources depending on
> On Tuesday 28 March 2006 12:32, Emil Dotchevski wrote:
>> I have:
>> alias test : test-cygwin : <toolset>gcc ;
>> alias test : test-win32 : <toolset>msvc ;
>> I get this:
>> warning: toolset gcc initialization: can't find tool g++
>> warning: initialized from
>> C:/code/bin/boost-build/build\targets.jam:756: in generate-really from
>> module object(main-target)@68
>> error: failed to build ./test with properties <debug-symbols>on
> I can't reproduce this. Either you have out-of-date Boost.Build, or you
> with a compiler that's neither gcc nor msvc.
> - Volodya
> Vladimir Prus
> Boost.Build V2: http://boost.org/boost-build2
> Unsubscribe & other changes:
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