Ben Hutchings <yg-boost-users@m.gmane.org> writes:
This is correct. The 'debug' configuration is meant to work with a release version of Python, though I don't know why. However, there is no need to modify the Jamfile; just use the 'debug-python' configuration instead. Also, make sure you include <pyconfig.h> before any of the Boost.Python headers, because not all of them do that and you can end up with incorrect structure definitions in a debug build if you don't. (I should report this bug.)
Ralf says:
However, there is no need to modify the Jamfile; just use the 'debug-python' configuration instead. Also, make sure you include <pyconfig.h> before any of the Boost.Python headers, because not all of them do that and you can end up with incorrect structure definitions in a debug build if you don't. (I should report this bug.)
We know about it; it only affects a few platforms and we think we have the right answer for the next release, IIRC. Ralf can confirm/deny that, though...
We know about it, but I don't think we have the right answer. I was hoping the right answer is to include <pyconfig.h> before any system header on all platforms, but we found out the hard way that this leads to problems with VC and Codewarrior under Windows. We still need to look at this issue very carefully and do a lot of testing on all platforms with all combinations of debug, debug-python and release builds. At the moment I am thinking a start would be to rework boost/python/detail/wrap_python.hpp and include it everywhere we currently have the Tru64-only <pyconfig.h> includes in the 1.30.0 release. -- Dave Abrahams Boost Consulting www.boost-consulting.com