ksmith
October 19, 2017, 6:20pm
4
Take a look at these recent topics. This issue has been discussed quite frequently on the forum lately. There are also other topics that can be found using the search that should help you.
On my mac this is the stock python. The following command will tell you where the python that is being executed lives:
which python
which python2
I believe that by default the system python comes first in the path and may be the reason that the homebrew version is not being evoked. This will list the search paths for binaries:
printenv PATH
This will let you locate all the files named python on the system, one will be the system python and one will be homebrew:
locate */python
This is typ…
@ksmith So it looks like you’re right. It’s an issue with SIP that can be worked around using a different, non-system python. However, that one flag alone is not enough. I had to do:
cmake -Dall=On -DPYTHON_EXECUTABLE=/usr/local/bin/python2 -DPYTHON_INCLUDE_DIR=/usr/local/Cellar/python/2.7.14/Frameworks/Python.framework/Versions/2.7/Headers -DPYTHON_LIBRARY=/usr/local/Cellar/python/2.7.14/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib ../root/
pointing it at the Homebrew vers…