8000 top level cmake build doesn't forward Python_EXECUTABLE, Python_LIBRARY, Python_INCLUDE_DIR to gravity_external · Issue #225 · aphysci/gravity · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

top level cmake build doesn't forward Python_EXECUTABLE, Python_LIBRARY, Python_INCLUDE_DIR to gravity_external #225

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

Open
JaredDiCioccio opened this issue Sep 28, 2024 · 0 comments · May be fixed by #226

Comments

@JaredDiCioccio
Copy link
Contributor

In some environments it might be necessary to specify a specific Python distribution when building. This can be done via command line switches, for example:

-DPython_EXECUTABLE=/usr/bin/python3.8
-DPython_LIBRARY=/usr/lib/python3.8/config-3.8-aarch64-linux-gnu/libpython3.8.so
-DPython_INCLUDE_DIR=/usr/include/python3.8

Doing so allows the cmake FindPython macros to find the appropriate libraries when linking.

However these values do not get passed down to the gravity_external projects, so effectively get ignored, resulting in gravity python libs being linked against a potentially wrong version of Python.

@JaredDiCioccio JaredDiCioccio linked a pull request Sep 28, 2024 that will close this issue
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 a pull request may close this issue.

1 participant
0