On Feb 15, 2009, at 8:15 PM, Robert Haines wrote:
I'd be interested in your feedback if you look at them. I don't have
a situation at the moment where I need a certain version of python
for my code which is why this issue totaly past me by so far.
The scripts included worked well. I create
On 11 Feb 2009, at 17:57, Enrico Franchi wrote:
On Feb 11, 2009, at 1:14 PM, Robert Haines wrote:
I've had a quick look at FindPythonInterp and FindPythonLibs and
they are inconsistent!
If you add a line to print PYTHON_EXECUTABLE you will see that it
finds /opt/local/bin/python2.6 but
Maybe file a bug? Do you want to or shall I?
Actually, it's more or less this one here:
http://public.kitware.com/Bug/view.php?id=2257
Rob
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/
On 10 Feb 2009, at 20:59, Enrico Franchi wrote:
I have python_select and python2.6 is selected. /opt/local/bin is
before /usr/bin.
However
MESSAGE(${PYTHON_INCLUDE_PATH})
says:
/System/Library/Frameworks/Python.framework/Headers
Hmm, you're right. Just tested on mine and it gets it wrong
What is the best way to have my own Python version detected?
What is the rule cmake uses to choose the Python installation to use?
What I do is that I have the python_select package installed and then /
opt/local/bin in my path before /usr/bin. Then you can select which
python you want with
I've got Python 2.6 installed with MacPorts (MacOS X 10.5),
thus the framework is in /opt/local/Library/Frameworks.
CMake always finds system Python (FIND_PACKAGE(PythonLibs)).
I have already tried hacking CMakeFindFrameworks in order to add /opt/
local/Library/Framework to
the searched paths.
