Building with 1.0.3 package has linking errors
jdm opened this issue · 4 comments
When I tried upgrading the NuGet package in this project to the latest version, I received undefined symbols when linking for all of the extension APIs (eg. xrGetD3D11GraphicsRequirementsKHR).
The loader does not export extension functions starting with 1.0.3. We've held off upgrading because the loader also has a bug which causes it to crash when using XrSpace handle created from an extension function (the spatial anchor extension). Hopefully the 1.0.6 or 1.0.7 loader will have the fix for this. This is why we've held off upgrading to the newer NuGet version.
FYI, once the change goes in to fix the problem in the loader (KhronosGroup/OpenXR-SDK-Source#146) it will only support a single XrInstance at a time.
Apps will be required to use xrGetInstanceProcAddr to get function pointers for extension functions instead of statically linking to the loader. In the future we'll probably add some helper code to make this easier, something like GLEW.
(You can already use OpenXR-HPP which has exactly such a dispatch-table helper integrated in its design)