>> 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? David> Considering that v2 was released a few weeks ago, that sounds David> about right ;-) How about OTHER=<the other include directory make -n \ | sed -e "s/-I$PYTHON_INCLUDES/-I$PYTHON_INCLUDES -I$OTHER/" \ | sh -x ? Depending on how the boost::python directory tree is organized, it just might work. Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4