Skip Montanaro <skip@pobox.com> writes:
>> Now the problem is that boost::python, and other packages, gives you >> one variable, like PYTHON_INCLUDES, for its build. When it is set to >> find `Python.h' it will not find `pyconfig.h'.
Seems to me like boost::python needs to be able to point at both directories. Maybe PYTHON_INCLUDES could be a colon-separated list of directories which gets broken up into multiple -I<dir> flags. I suppose that sort of change is a bit late for v1?
Considering that v2 was released a few weeks ago, that sounds about right ;-) -- David Abrahams dave@boost-consulting.com * http://www.boost-consulting.com Building C/C++ Extensions for Python: Dec 9-11, Austin, TX http://www.enthought.com/training/building_extensions.html