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

[openxr-loader] update to 1.1.45 and get error: Python 3 not found #532

Closed
JonLiu1993 opened this issue Feb 12, 2025 · 6 comments
Closed

Comments

@JonLiu1993
Copy link

Hi, when I update openxr-loader to the latest version 1.1.45, I get this error in vcpkg test pipline:
microsoft/vcpkg#43763

CMake Error at src/CMakeLists.txt:433 (message):
  Python 3 not found, but pre-generated
  D:/b/openxr-loader/src/ase-1.1.45-1760c881e2.clean/src/xr_generated_dispatch_table.h
  not found

I noticed in the vcpkg portfile.cmake there already have pass option "-DPYTHON_EXECUTABLE=${PYTHON3}",
So I add "-DPython3_EXECUTABLE=${PYTHON3}" fix this error, I want to know the latest version openxr-loader need pass all option? Thanks!

@dg0yt
Copy link

dg0yt commented Feb 12, 2025

IOW there is inconsistent use of CMake python modules and variables. It would be great to see consistency restored.

@rpavlik
Copy link
Contributor

rpavlik commented Feb 12, 2025

We switched from the deprecated way of finding the Python interpreter to the current recommended one, see #486

So yes, if Python cannot be found by default, the config variable to pass has indeed changed, to match other CMake based builds.

Does this answer your question?

@dg0yt
Copy link

dg0yt commented Feb 13, 2025

Update: AFAIU PYTHON_EXECUTABLE still occurs in test-related third-party code. In some cases it seems to be initialized from Python3_EXECUTABLE. I do not know if this covers all cases.
https://github.com/search?q=repo%3AKhronosGroup%2FOpenXR-SDK-Source%20PYTHON_EXECUTABLE&type=code

This code is not used in vcpkg. In fact, the vcpkg build clearly reports that PYTHON_EXECUTABLE is not used in that configuration, and the issue is obsolete from the vcpkg POV.

@rpavlik
Copy link
Contributor

rpavlik commented Feb 13, 2025

The code in that code search is self-test code from dependencies that is never built in OpenXR, so PYTHON_EXECUTABLE should not ever be used in the build or need to be set. it is consistent and that fix resolved some deprecation warnings.

So what needs to be done to fix this issue? I'm not sure what the repro steps or success criteria are here.

(While I use vcpkg, I do not usually use the OpenXR loader from vcpkg. We do ship binaries with CMake configuration files with each release, though I have no idea if anyone actually uses them.)

@dg0yt
Copy link

dg0yt commented Feb 13, 2025

No fix needed here. You may close the issue.

@rpavlik
Copy link
Contributor

rpavlik commented Feb 13, 2025

Great, thanks for the confirmation.

@rpavlik rpavlik closed this as completed Feb 13, 2025
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

No branches or pull requests

3 participants