|
Boost-Build : |
From: David Abrahams (dave_at_[hidden])
Date: 2006-04-28 17:59:27
>From the NT shell, building in libs/python/test, consider these two
command-lines:
v1:
"/usr/local/gcc-4.0.2\bin\g++" -c -DUSE_DL_IMPORT -DBOOST_PYTHON_DYNAMIC_LIB -g -O0 -fno-inline -Wall -ftemplate-depth-255 -I"..\..\..\bin\boost\libs\python\test" -I "c:\boost" -I "..\..\.." -I "\usr\include\python2.4" -o "..\..\..\bin\boost\libs\python\test\polymorphism_ext.pyd\gcc-4.0.2\debug\polymorphism.obj" "polymorphism.cpp"
v2:
"/usr/local/gcc-4.0.2/bin/g++.exe" -ftemplate-depth-100 -O0 -fno-inline -Wall -g -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_DYNAMIC_LIB -DBOOST_PYTHON_SUPPRESS_REGISTRY_INITIALIZATION -I"..\..\.." -I"c:\python24\include" -c -o "..\..\..\bin.v2\libs\python\test\polymorphism.test\gcc-4.0.2\debug\threading-multi\polymorphism.o" "polymorphism.cpp"
First of all, I wonder why they're so different. For example, why is
-DBOOST_PYTHON_SUPPRESS_REGISTRY_INITIALIZATION present?!? And why
-DBOOST_ALL_NO_LIB?
Secondly, the v2 command-line yields compile-time errors.
c:/python24/include/intobject.h:41: error: '__int64' does not name a type
c:/python24/include/longobject.h:37: error: '__int64' was not declared in this scope
c:/python24/include/longobject.h:39: error: '__int64' does not name a type
c:/python24/include/longobject.h:40: error: '__int64' does not name a type
...
I think that's because I haven't configured it to use my cygwin python
when building with GCC. I see cygwin-condition in python.jam, but I
don't think that does what I need it to.
What's it going to take to get this working in v2?
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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