Quote:
Originally Posted by mapreri
I can only do assumptions on why NO_DEFAULT_PATH was used (=> avoiding linking to system python?).
|
I've no idea myself, to tell you the truth. I inherited the FindPythonLibs.cmake file -- lock, stock and barrel. Not being particularly
fluent in cmake-ese, I made it work for me--and never looked back. Kevin also had to modify it to work on OSX, I believe.
It was certainly not MY intention to avoid linking to system python. Quite the contrary, in fact. That's why I included the x86_64-linux-gnu and the /i386-linux-gnu paths in the first place.
I'll gladly remove the NO_DEFAULT_PATH if it will expand the search and work for more architectures. Those who might not
want to link to the system python can still explicitly specify the python they want to utilize.