Randy Heiland wrote:
Hello,
I'll post this in case someone knows the answer, while I go searching...
I want to specify a non-system Python to be used, so I set the following
in my CMakeCache.txt (obviously, I'm on OSX):
PYTHON_DEBUG_LIBRARY:FILEPATH=<path-to-my>/Python.framework
PYTHON_EXECUTABLE:FILEPATH=/usr/local/bin/python2.6
PYTHON_INCLUDE_PATH:PATH=<path-to-my>/Python.framework/Headers
PYTHON_DEBUG_LIBRARY:FILEPATH=<path-to-my>/Python.framework
However, re-config'ing, both of the LIB vars get reset to the system
Python:
PYTHON_DEBUG_LIBRARY:FILEPATH=-framework Python
PYTHON_LIBRARY:FILEPATH=-framework Python
I'm able to get away with doing this, i.e. specify non-system Python,
for another cmake-based project. I'm guessing the problem has to do
with FindPythonLibs.cmake
Hmm. So setting those manually in your cmake cache triggers a reconf
for boost-cmake, but not the other project you speak of?
-t
_______________________________________________
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
