Bring RiftLift's native Linux XR runtime in-tree - #1
Merged
Conversation
This file contains hidden or 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
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.
What changed
wineopenxr.dll/wineopenxr.soto call Linux OpenXR;vrclient_x64.dll/vrclient_x64.soand RiftLift's pinned XRizer build;bin/linux64/vrclient.solayout;Why
RiftLift previously depended on separately maintained compatibility forks and host-provided runtime state. That made installation fragile and allowed local development trees to hide packaging errors. This consolidates the complete application compatibility layer in one repository and sends XR calls directly through Proton's in-process PE-to-ELF boundary into the user's Linux OpenXR runtime.
The final packaging failure found during validation was that Proton resolves an OpenVR override at
bin/linux64/vrclient.so, while the first release artifact only containedlibxrizer.soat its root. The installer now creates the standard Proton runtime layout from the pinned payload.User impact
Users with a working Linux OpenXR setup can install RiftLift through the normal GUI/CLI flow without separately installing or configuring Revive, XRizer, SteamVR, or a compatibility daemon. Explicit runtime overrides remain available for development.
Validation
78 passedin the Python test suite;Release candidate: v0.9.0-alpha.3