On 09.07.2012 10:26, Tim Blechmann wrote:
.... there are still some test failures on win32, but i think i found the reason and fixed the tests (btw it is rather time consuming to work with the test farm as the win32 tests are only run about once a week).
I'm trying to setup the regression tests on our build server and I have some problems with specifying the toolset(s). The command line is: C:\Python27\python.exe run.py --runner=MSVC9_x64_DoctorWeb --toolsets=msvc-9.0 --bjam-options=architecture=x86 --bjam-options=address-model=64 --tag=branches/release --force-update --bjam-options="-j 10" In the bjam.log, I see: warning: No toolsets are configured. warning: Configuring default toolset "msvc". warning: If the default is wrong, your build may not work correctly. warning: Use the "toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html notice: [msvc-cfg] msvc-10.0 detected, command: 'C:\program files (x86)\microsoft visual studio 10.0\VC\bin\cl.exe' notice: [msvc-cfg] msvc-9.0 detected, command: 'C:\program files (x86)\microsoft visual studio 9.0\VC\bin\cl.exe' notice: will use 'C:\program files (x86)\microsoft visual studio 10.0\VC\bin\cl.exe' for msvc, condition <toolset>msvc-10.0 notice: [msvc-cfg] condition: '<toolset>msvc-10.0/<architecture>/<address-model>', setup: 'call "C:\program files (x86)\microsoft visual studio 10.0\VC\vcvarsall.bat" x86 >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-10.0/<architecture>/<address-model>32', setup: 'call "C:\program files (x86)\microsoft visual studio 10.0\VC\vcvarsall.bat" x86 >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-10.0/<architecture>x86/<address-model>', setup: 'call "C:\program files (x86)\microsoft visual studio 10.0\VC\vcvarsall.bat" x86 >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-10.0/<architecture>x86/<address-model>32', setup: 'call "C:\program files (x86)\microsoft visual studio 10.0\VC\vcvarsall.bat" x86 >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-10.0/<architecture>/<address-model>64', setup: 'call "C:\program files (x86)\microsoft visual studio 10.0\VC\vcvarsall.bat" x86_amd64 >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-10.0/<architecture>x86/<address-model>64', setup: 'call "C:\program files (x86)\microsoft visual studio 10.0\VC\vcvarsall.bat" x86_amd64 >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-10.0/<architecture>ia64/<address-model>', setup: 'call "C:\program files (x86)\microsoft visual studio 10.0\VC\vcvarsall.bat" x86_ia64 >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-10.0/<architecture>ia64/<address-model>64', setup: 'call "C:\program files (x86)\microsoft visual studio 10.0\VC\vcvarsall.bat" x86_ia64 >nul ' C:/Users/BoostTest/Release/tools_bb/build\feature.jam:308: in implied-subfeature from module feature error: "9.0" is not a known subfeature value of <toolset>msvc C:/Users/BoostTest/Release/tools_bb/build\feature.jam:491: in validate-value-string from module feature C:/Users/BoostTest/Release/tools_bb/build\feature.jam:358: in expand-subfeatures-aux from module feature C:/Users/BoostTest/Release/tools_bb/build\feature.jam:419: in feature.expand-subfeatures from module feature C:/Users/BoostTest/Release/tools_bb/build\build-request.jam:20: in apply-to-property-set from module build-request C:/Users/BoostTest/Release/tools_bb/kernel\modules.jam:103: in modules.call-in from module build-request C:/Users/BoostTest/Release/tools_bb/util\sequence.jam:48: in sequence.transform from module sequence C:/Users/BoostTest/Release/tools_bb/build\build-request.jam:32: in build-request.expand-no-defaults from module build-request C:/Users/BoostTest/Release/tools_bb\build-system.jam:630: in load from module build-system C:\Users\BoostTest\Release\tools_bb/kernel\modules.jam:283: in import from module modules C:\Users\BoostTest\Release\tools_bb/kernel/bootstrap.jam:142: in boost-build from module C:\Users\BoostTest\Release\boost\boost-build.jam:17: in module scope from module What am I doing wrong? -- Sergey Cheban
Le 12/07/12 11:38, Sergey Cheban a écrit :
On 09.07.2012 10:26, Tim Blechmann wrote:
.... there are still some test failures on win32, but i think i found the reason and fixed the tests (btw it is rather time consuming to work with the test farm as the win32 tests are only run about once a week).
I'm trying to setup the regression tests on our build server and I have some problems with specifying the toolset(s).
The command line is: C:\Python27\python.exe run.py --runner=MSVC9_x64_DoctorWeb --toolsets=msvc-9.0 --bjam-options=architecture=x86 --bjam-options=address-model=64 --tag=branches/release --force-update --bjam-options="-j 10"
What am I doing wrong?
Have you declared a toolset msvc-9.0 in your user-config.jam file? Vicente
On 12.07.2012 15:23, Vicente J. Botet Escriba wrote:
The command line is: C:\Python27\python.exe run.py --runner=MSVC9_x64_DoctorWeb --toolsets=msvc-9.0 --bjam-options=architecture=x86 --bjam-options=address-model=64 --tag=branches/release --force-update --bjam-options="-j 10"
What am I doing wrong?
Have you declared a toolset msvc-9.0 in your user-config.jam file? No I hadn't. After I created user-config.jam and specified it in the command line, all seems to be ok.
Btw, is it possible to specify multiple toolsets in the user-config.jam? According to the http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Build_V... it seems to be possible, but I tried it without success. -- Sergey Cheban
Hi.
Btw, is it possible to specify multiple toolsets in the user-config.jam? According to the http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Build_V...
it seems to be possible, but I tried it without success.
What exactly did you try and what were the results? user-config.jam, site-config.jam & project-config.jam are configuration files loaded by Boost Build at startup (actually test-config.jam as well but that one's kinda special). They may be used to configure one or more different toolsets available on the system. For instance, a project-config.jam I'm using at the moment for something contains:
local cygwin-bin = "c:/PROGRA~2/Cygwin/bin" ; using gcc : 3 : $(cygwin-bin)/g++-3.exe : <archiver>$(cygwin-bin)/ar.exe <ranlib>$(cygwin-bin)/ranlib.exe ;
using msvc : 9.0 ;
As you can see - it can configure multiple toolsets. You can also easily configure multiple versions of a single toolset (if supported by the specific toolset you are configuring) as in:
using msvc : 9.0 ; using msvc : 10.0 ;
Or a toolset may support some customized initialization syntax, e.g. toolset msvc allows attempting to autodetect available toolset versions and configuring the toolset based on that automatically by specifying:
using msvc : all ;
Note that all this does not specify which toolset will actually be used for your build. It only configures specific toolsets in case some target needs to use them for its build. Usually this means that you still need to specify the toolset on the command line. Hope this helps. Best regards, Jurko Gospodnetić
participants (3)
-
Jurko Gospodnetić -
Sergey Cheban -
Vicente J. Botet Escriba