OpenXR-SDK-Source
OpenXR-SDK-Source copied to clipboard
KhronosGroup
multilib/multiarch runtime selection on Linux
Yeah, though if the loader keeps searching when dlopen returns an error it should Just Work.
@Ralith so you'd just install different file names for the 32-bit and 64-bit manifest so they both can coexist?
Hmm - but they can't both be active_runtime.json
Oh, right, I was thinking in Vulkan loader terms. Yeah, this is a problem; probably the json format will need to be changed. How is it handled on Windows?
On Thu, Oct 24, 2019, 12:01 Ryan A. Pavlik [email protected] wrote:
@Ralith https://github.com/Ralith so you'd just install different file names for the 32-bit and 64-bit manifest so they both can coexist?
Hmm - but they can't both be active_runtime.json
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/KhronosGroup/OpenXR-SDK-Source/issues/142?email_source=notifications&email_token=AAAZQ3UAVR252UACXOLLXR3QQHWHVA5CNFSM4JESHC42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECGCW6Q#issuecomment-546057082, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQ3SHNI3NGYSBSEEGXN3QQHWHVANCNFSM4JESHC4Q .
Windows has separate registry keys for 32bit and 64bit. A Linux equivalent solution would be different well known file names or different well known file paths for the json. IMO, Ideally we keep the json schema unchanged.
Updating the schema has advantages: it allows XR_RUNTIME_JSON to work for all processes, and makes it impossible to forget to update one of multiple files. I don't think the amount of breakage would be much different, either.
On Thu, Oct 24, 2019, 12:26 Bryce Hutchings [email protected] wrote:
Windows has separate registry keys for 32bit and 64bit. A Linux equivalent solution would be different well known file names or different well known file paths for the json. IMO, Ideally we keep the json schema unchanged.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/KhronosGroup/OpenXR-SDK-Source/issues/142?email_source=notifications&email_token=AAAZQ3X6C32TFEIEOEJDJMDQQHZFNA5CNFSM4JESHC42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECGFBPY#issuecomment-546066623, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQ3T7FGFSP5VWTV52ATDQQHZFNANCNFSM4JESHC4Q .
well, but it would introduce a difference between platforms: right now, there's only one runtime manifest parser used all over.
(I'm in favor of either decorated active_runtime.json filename, or a pattern of active_runtime.json files and it tries until it succeeds in loading from one of them)
I suppose we could make XR_RUNTIME_JSON a delimited list, too, and there might be other applications for trying multiple runtimes.
On Fri, Oct 25, 2019, 05:53 Ryan A. Pavlik [email protected] wrote:
(I'm in favor of either decorated active_runtime.json filename, or a pattern of active_runtime.json files and it tries until it succeeds in loading from one of them)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/KhronosGroup/OpenXR-SDK-Source/issues/142?email_source=notifications&email_token=AAAZQ3QP2O3E2W2FVW2DS3TQQLT4DA5CNFSM4JESHC42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECIIFUQ#issuecomment-546341586, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZQ3R4JM5VL7P5J5AIA33QQLT4DANCNFSM4JESHC4Q .
An issue (number 1277) has been filed to correspond to this issue in the internal Khronos GitLab.
If you have a Khronos account, you can access that issue at KHR:openxr/openxr#1277.
