Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2004-08-24 08:41:07

Rene Rivera <grafik.list_at_[hidden]> writes:

> Rene Rivera wrote:
>>>>Toon Knapen <toon.knapen_at_[hidden]> writes:
>>>>>Since version 1.134 of boost/tools/build/v1/boost-base.jam (created on
>>>>>the 12th of August) the libraries (specified by means of <find-library>
>>>>>in the requirements section of the exe) are sorted lexicographically. On
>> Yep, it was me, although not intentionally. I just did not realize
>> sorting the properties would also sort the <find-library> requirements.
>> I'll fix it soon.
> OK, should be fixed now.

Unfortunately, something new broke. Now when I run tests I'm seeing:

execute-test c:\build\bin\tmp\foo.test\cwpro9\debug-python\threading-multi\

set PATH=c:/tools/cwpro9\Win32-X86 Support\Libraries\Runtime;c:/tools/cwpro9\Win32-X86 Support\Libraries\Runtime\Libs\MSL_ALL-DLLs;%PATH%
c:\build\bin\tmp\foo.test\cwpro9\debug-python\threading-multi\foo.exe <sysinclude>@boost > c:\build\bin\tmp\foo.test\cwpro9\debug-python\threading-multi\foo.output 2>&1

Note the <sysinclude>@boost in the previous line. That screws
testing up completely.

Dave Abrahams
Boost Consulting

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at