Re: [CMake] Finding the correct Python framework with cmake

Jed Brown wrote: Mark Moll wrote: Add "-F /opt/local/Library/Frameworks" to your compilation flags or add this line to your .bash_profile: You should never add the -F to the CMake flags, just use the full path to the framework dir in either an include or a link library and CMake will add the

Re: [CMake] Finding the correct Python framework with cmake

Mark Moll wrote: > Add "-F /opt/local/Library/Frameworks" to your compilation flags or > add this line to your .bash_profile: > > export DYLD_FRAMEWORK_PATH=/opt/local/Library/Frameworks It seems to me that the only acceptable solution is that FindPythonInterp.cmake and FindPythonLibs.cmake consu

Re: [CMake] Finding the correct Python framework with cmake

Add "-F /opt/local/Library/Frameworks” to your compilation flags or add this line to your .bash_profile: export DYLD_FRAMEWORK_PATH=/opt/local/Library/Frameworks On Nov 11, 2009, at 4:15 PM, Celil Rufat wrote: > I am using the macports version of python on a Snow Leopard computer, and > using

[CMake] Finding the correct Python framework with cmake

I am using the macports version of python on a Snow Leopard computer, and using cmake to build a cross-platform extension to it. include(FindPythonInterp) include(FindPythonLibs ) However, while cmake identified the correct interpreter in /opt/local/bin, it tries to link against the wrong frame