Deployment story for layers on Windows?

[rpavlik]

Was working on some CI things, and I realized I don't actually know the deployment story (and thus, a reasonable layout) of the layers on Windows. (for the loader, I just matched the vulkan one which is a mostly-linuxy-layout with "32" suffixes.)

cc @daveh-lunarg

[daveh-lunarg]

I think following the Vulkan model is as good as any, with layers as a peer of loader - i.e. SDK_root/src/layers/ - just as it's currently laid out in this repo.

If you're asking about binaries (and I'm not sure we want those in the -SDK repo?), there are Bin and Bin32 directories that are peers of src

[rpavlik]

I mean, how does an end-user-developer actually use them? Look at the binaries included with the openxr-sdk releases to see what I've done so far, this is just re-arranging things after doing essentially "make install", using azure-pipelines https://github.com/rpavlik/OpenXR-SDK-Source/tree/azure/.azure-pipelines (yes I have to rebase that branch every release to get binaries...)

[rpavlik-bot]

An issue (number 1276) 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#1276.