Re: [Boost-users] [general] boost 1.35.0 library naming and bjam arguments priorities
hi,
for building boost 1.35.0 with bjam 3.1.16 and mingw gcc 3.4.5 on winxp sp2 i created a *.BAT-file like follows:
@echo off SETLOCAL SET MINGW=C:\Development_Compiler\MinGW SET PYTHN=C:\Development_Compiler\Python25 SET BUILD=C:\Development_Libs\Boost_v1.35.0 SET path=C:\WINDOWS;C:\WINDOWS\system32;%MINGW%\Bin cls bjam.exe -a "-sTOOLS=mingw" "-sGCC_ROOT_DIRECTORY=%MINGW%" "-sPYTHON_ROOT=%PYTHN%" "-sPYTHON_VERSION=2.5"
All the -s option above have no effect.
--link=static --runtime-link=static --threading=single --optimization=on --toolset=gcc --build-dir=%BUILD% --build-type=complete install ENDLOCAL
Remove "--" in front of all properties. "--build-dir" and "--build-type" are options and need "--". Everything else is properties, which tell what flavour of binaries you want to get, and don't need "--".
- Volodya
hi volodya and all others, thanks for your responses. a) but there is one thing i don't understand. why i got libs like boost_xyz.a boost_xyz.dll libboost_xyz.a without doing any rename while builing boost 1.34.1 with bjam 3.1.15? b) why the -s options have no effect? version "-sPYTHON_VERSION=2.5" of desired python and libpython25.a in "-sPYTHON_ROOT=%PYTHN%" (...\lib) is found by bjam. finally it compiles and works well (boost 1.34.1 with bjam 3.1.15 and nearly identical BAT-file). aside from this, http://www.boost.org/doc/tools/build/doc/html/jam/usage.html says -s var=value set the variable var to value, overriding both internal variables and variables imported from the environment. Command-line and Environment Variable Quoting ... Boost Jam remedies that by treating all such settings as a single string if they are surrounded by double-quotes. ... (all surrounding by me, and not only the value part) daniel ____________________________________________________________________ Ihre Messenger, Communities und E-Mails jetzt in einem Programm! WEB.DE MultiMessenger http://www.produkte.web.de/messenger/?did=3071
damny@web.de wrote:
hi volodya and all others,
thanks for your responses.
a) but there is one thing i don't understand. why i got libs like boost_xyz.a boost_xyz.dll libboost_xyz.a without doing any rename while builing boost 1.34.1 with bjam 3.1.15?
Because behaviour was changed to what is considered better one.
b) why the -s options have no effect? version "-sPYTHON_VERSION=2.5" of desired python and libpython25.a in "-sPYTHON_ROOT=%PYTHN%" (...\lib) is found by bjam. finally it compiles and works well (boost 1.34.1 with bjam 3.1.15 and nearly identical BAT-file). aside from this, http://www.boost.org/doc/tools/build/doc/html/jam/usage.html says
-s var=value set the variable var to value, overriding both internal variables and variables imported from the environment.
Command-line and Environment Variable Quoting ... Boost Jam remedies that by treating all such settings as a single string if they are surrounded by double-quotes. ... (all surrounding by me, and not only the value part)
While -s option behave as documented, setting variable named PYTHON_VERSION does not affect anything, since Boost 1.34, I believe. In Boost.Build V2, instead of configuring everything on the command line, you can just put those configurations in user-config.jam - Volodya
participants (2)
-
damny@web.de
-
Vladimir Prus