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
The existing SDK CMake code uses python to generate a number of artifacts, but also uses the PYTHONPATH environment variable to ensure that common modules can be loaded.
However, while trying to create an openxr port for vcpkg, I've discovered that vcpkg provides an embedded version of python. Embedded versions of python from version 3.5.1 and on ignore the PYTHONPATH variable and this is apparently by design.
I'm investigating what needs to happen to make the OpenXR build work with either a conventional Python3 installation or an embedded one.
The text was updated successfully, but these errors were encountered:
I've opened a PR for the embedded python issue with #46 but I consider the other patch to be a pack, since it hard-codes library names. However I can update my existing PR #44 to use a similar approach but use the find_package(X11) mechanism for the libraries instead of hard-coding them.
The existing SDK CMake code uses python to generate a number of artifacts, but also uses the
PYTHONPATH
environment variable to ensure that common modules can be loaded.However, while trying to create an openxr port for vcpkg, I've discovered that vcpkg provides an embedded version of python. Embedded versions of python from version 3.5.1 and on ignore the
PYTHONPATH
variable and this is apparently by design.I'm investigating what needs to happen to make the OpenXR build work with either a conventional Python3 installation or an embedded one.
The text was updated successfully, but these errors were encountered: