Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve python and numpy detection - fixes #12 #13

Merged
merged 1 commit into from
Jul 25, 2014

Conversation

mcs07
Copy link
Contributor

@mcs07 mcs07 commented Jul 24, 2014

This should more explicitly help cmake locate the proper python and numpy paths.

I think this should fix issue #12, although it is a bit hard to test because I can't replicate the issue.

python_prefix = %x(#{python_executable} -c 'import sysconfig;print(sysconfig.get_config_var("prefix"))').chomp
python_include = %x(#{python_executable} -c 'import sysconfig;print(sysconfig.get_path("include"))').chomp
python_version = "python" + %x(#{python_executable} -c 'import sys;print(sys.version[:3])').chomp
args << "-DPYTHON_EXECUTABLE='#{python_executable}'"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the main cause of issue #12 is that PYTHON_EXECUTABLE isn't set when using homebrew python, and this is used by FindNumPy.cmake to set PYTHON_NUMPY_INCLUDE_PATH.

However, PYTHON_NUMPY_INCLUDE_PATH is still somehow set correctly on my machine, but this clearly isn't the case for everyone.

greglandrum added a commit that referenced this pull request Jul 25, 2014
Improve python and numpy detection - fixes #12
@greglandrum greglandrum merged commit 49aafe9 into rdkit:master Jul 25, 2014
@mcs07 mcs07 deleted the numpy branch July 25, 2014 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants