top level cmake build doesn't forward Python_EXECUTABLE, Python_LIBRARY, Python_INCLUDE_DIR to gravity_external · Issue #225 · aphysci/gravity · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: