Find another solution to find python in cmake

[svkurowski]

Finding Python with cmake will not work on OS X if python3 is installed via homebrew.
See the cmake issue, the homebrew issue and #16 . There has not been any activity regarding the cmake issue since April.
An alternative solution is this cmake module. It's licensed under BSD. Details regarding licensing can be found here.
For a temporary fix when using homebrewed python3, use the following to configure the project *you might need to adjust the version):

  --raw-cmake-args \
  -DPYTHON_INCLUDE_DIR=/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework/Versions/3.4/include/python3.4m/ \
  -DPYTHON_LIBRARY=/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework/Versions/3.4/lib/libpython3.4.dylib \
  -DPython_FRAMEWORKS=/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework

[mic-e]

To clarify, is this an issue with homebrew, cmake, or both? Not a legal expert, but I don't think including BSD-licensed code poses a problem in any way. I'm more worried about breaking functionality on other platforms.

[svkurowski]

It's a cmake issue. The official FindFrameworks and FindPythonLibs modules don't recognize homebrew supplied Frameworks (which get installed to /usr/local/Frameworks/).
And Python is packed as a Framework on OS X.
Additionally FindFrameworks doesn't even allow to specify additional Frameworks folders.

[mic-e]

Hm... doesn't sound like a fix will be coming soon, then... I vote to include the qgis module.

[mic-e]

Note: All sorts of linux distros (mostly ubuntu) seem to have issues with the current way of finding Python as well.

[thehydroimpulse]

You might also need to add -DPYTHONLIBS_VERSION_STRING=3.4.1 given the recent change.

[TheJJ]

should be fixed by the separate cmake module, if not: reopen pls.