more-precise instructions for "Python.h first"?
Boost.Python is now trying hard to accomodate the "Python.h before
system headers rule". Unfortunately, we still need a wrapper around
Python.h, at least for some versions of Python, so that we can
work around some issues like:
//
// Python's LongObject.h helpfully #defines ULONGLONG_MAX for us
// even when it's not defined by the system which confuses Boost's
// config
//
To cope with that correctly, we need to see
participants (4)
-
David Abrahams
-
Jack Jansen
-
martin@v.loewis.de
-
Tim Peters