building 32 Bit and 64 Bit extensions on the same machine
Dear all, I want to build 32 bit extensions and 64 bit extensions on my Windows 7 / 32 Bit with boost. After two days of checking google I am a bit frustrated. I am new to Boost and it is a bit like a jungle. Can anyone help on what I need to do to set up Boost in the right way and have a Jamroot which allows me to compile my Python extensions in 32 Bit and 64 Bit at the same time (with MSVC 2008). Thanks a lot, Ronny
Hi, add address-model=64 to Boost::Python bjam compilation command and that's all. Be aware, that not all MSVS versions (e.g. Express Edition) are equipped with 64 Bit compiler. 2012/8/24 Ronny Herzog <herzog@mpi-cbg.de>:
Dear all,
I want to build 32 bit extensions and 64 bit extensions on my Windows 7 / 32 Bit with boost. After two days of checking google I am a bit frustrated. I am new to Boost and it is a bit like a jungle.
Can anyone help on what I need to do to set up Boost in the right way and have a Jamroot which allows me to compile my Python extensions in 32 Bit and 64 Bit at the same time (with MSVC 2008).
Thanks a lot, Ronny
_______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
Thank you, but this does not seem to work. If I do this with "bjam --address-model=64 -n" I can see that it does compile it with my 32Bit Python and without setting the x86_AMD64 flag: "[...] file C:\boost_1_50_0\bin.v2\libs\python\build\msvc-9.0\release\threading-multi\o bject\iterator.obj.rsp "C:\boost_1_50_0\libs\python\src\object\iterator.cpp" -Fo"C:\boost_1_50_0\bin.v2 \libs\python\build\msvc-9.0\release\threading-multi\object\iterator.obj" -TP /O2 /Ob2 /W3 /GR /MD /Zc:forScope /Zc:wchar_t /wd4675 /EHs -c -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG "-IC:\Python26\include" "-IC:\boost_1_50_0" compile-c-c++ C:\boost_1_50_0\bin.v2\libs\python\build\msvc-9.0\release\threadin g-multi\object\iterator.obj call "C:\Program Files\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" x86 >nu l cl /Zm800 -nologo @"C:\boost_1_50_0\bin.v2\libs\python\build\msvc-9.0\release\th reading-multi\object\iterator.obj.rsp" [...]" I am using MS Visual Studio 2008. Unfortunately, I cannot test it on an 64Bit machine right now. I have Python26 (32Bit) and Python26 (64Bit) installed and I guess I have to inform bjam somewhere which one to use. Thanks a lot, Ronny Am 8/24/2012 4:49 PM, schrieb Wojciech Mamrak:
Hi,
add address-model=64 to Boost::Python bjam compilation command and that's all. Be aware, that not all MSVS versions (e.g. Express Edition) are equipped with 64 Bit compiler.
2012/8/24 Ronny Herzog <herzog@mpi-cbg.de>:
Dear all,
I want to build 32 bit extensions and 64 bit extensions on my Windows 7 / 32 Bit with boost. After two days of checking google I am a bit frustrated. I am new to Boost and it is a bit like a jungle.
Can anyone help on what I need to do to set up Boost in the right way and have a Jamroot which allows me to compile my Python extensions in 32 Bit and 64 Bit at the same time (with MSVC 2008).
Thanks a lot, Ronny
_______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
On Mon, Aug 27, 2012 at 04:23:14PM +0200, Ronny Herzog wrote:
Thank you,
but this does not seem to work. If I do this with "bjam --address-model=64 -n"
Note that the previous poster did not say "--address-model=64". He said "address-model=64". It's a feature, not an option. Features do not have a leading dashdash. You may of course have to point out a suitable Python path anyway, but it helps if you actually instruct the build to be 64-bit in the first place. -- Lars Viklund | zao@acc.umu.se
Aha! Thank you. This made it work. Ronny Am 8/31/2012 3:34 AM, schrieb Lars Viklund:
On Mon, Aug 27, 2012 at 04:23:14PM +0200, Ronny Herzog wrote:
Thank you,
but this does not seem to work. If I do this with "bjam --address-model=64 -n"
Note that the previous poster did not say "--address-model=64". He said "address-model=64". It's a feature, not an option. Features do not have a leading dashdash. You may of course have to point out a suitable Python path anyway, but it helps if you actually instruct the build to be 64-bit in the first place.
participants (3)
-
Lars Viklund -
Ronny Herzog -
Wojciech Mamrak