On 02/02/2016 02:24 PM, Novosielski, Ryan wrote:
Apparently, though, setting PYTHON_INCLUDE_DIR to /anything/ (whether or not it contains Python.h) stops this error:
Right - this is a "feature" of cmake. If you set PYTHON_INCLUDE_DIR you are explicitly saying to cmake "believe me, I know where Python.h is - don't bother looking for it" and it will trust you blindly. Since it's such a sledgehammer solution to the problem, perhaps we shouldn't suggest that people set it, but rather set the corresponding search hint (PYTHON_INCLUDE_PATH, IIRC). I'll poke at it and see.
Ben -- ben@salilab.org https://salilab.org/~ben/ "It is a capital mistake to theorize before one has data." - Sir Arthur Conan Doyle