Use Khronos loader for Pico and add store required manifest entries #180
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BastiaanOlij
force-pushed
the
pico_khronos
branch
2 times, most recently
from
3ec1bab to
e5da86a
Compare
BastiaanOlij
force-pushed
the
pico_khronos
branch
from
e5da86a to
5ae1621
Compare
|
Changed this the same way as #182 so we no longer need to keep the khronos binaries in our repo but they are pulled in as dependencies by gradle |
m4gr3d
approved these changes
Jun 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of PICO OS 5.9.0, PICO now uses the Khronos loader and has deprecated their own SDK.
After investigating a support query through our forums for deploying a Godot app to the Pico store, we were pointed to the Pico Quickstart page.
The key missing ingredient is likely the
pvr.sdk.versionmanifest entry that now simply states "OpenXR" to indicate the Khronos loader is used.This PR alters the PICO entry to use the Khronos loader and adds this new manifest entry. I have not merged the PICO settings into the Khronos loader section as the PICO permission requirements clash with HTCs permission requirements. Our only solution at the moment is to keep these as separate entries.
But everything seems to work otherwise.