Refactor the project structure

[m4gr3d]

Refactor the project structure to reduce duplication of code, logic and build configs across the various vendors we support.

• Consolidate all the vendors modules into a single godotopenxr module with multiple vendors product flavors to allow for vendor-specific customizations
• Consolidate both gradle and cmake build configs
• Add GodotOpenXR.kt to consolidate common java/kotlin logic for the OpenXR vendors plugin implementations
• Move native code from the common directory to the godotopenxr/src/main/cpp directory

Note the changes in this PR are primarily due to file migration and updates of the logic and build configs as needed to match the new layout. No capabilities, functionality were added / removed / lost as part of the refactor.

[dsnopek]

Overall this looks good to me! I tested it locally, and everything seemed to work fine.

However, I wonder if we should call the directory godotopenxrvendors rather than just godotopenxr? I know this internally within the project, but I don't want to give the impression that this is adding OpenXR support to Godot in general (as opposed to just implementing vendor extensions).

[m4gr3d]

Overall this looks good to me! I tested it locally, and everything seemed to work fine.

However, I wonder if we should call the directory godotopenxrvendors rather than just godotopenxr? I know this internally within the project, but I don't want to give the impression that this is adding OpenXR support to Godot in general (as opposed to just implementing vendor extensions).

Sounds good to me. I went with godotopenxr to reflect the current structure; i.e: we're going from:

• godotopenxrkhronos
• godotopenxrlynx
• godotopenxrmeta
• godotopenxrpico

To:

• godotopenxr
  • khronos
  • lynx
  • meta
  • pico

We could also set the name to reflect its function (i.e: plugin) especially given the project will already be checked out within a godot_openxr_vendors root directory.

[dsnopek]

We could also set the name to reflect its function (i.e: plugin) especially given the project will already be checked out within a godot_openxr_vendors root directory.

Yeah, that makes sense! And plugin is shorter. :-) I think I personally like this option best so far

[m4gr3d]

We could also set the name to reflect its function (i.e: plugin) especially given the project will already be checked out within a godot_openxr_vendors root directory.

Yeah, that makes sense! And plugin is shorter. :-) I think I personally like this option best so far

Done!

[dsnopek]

Looks great!

I tested rebuilding and running the composition layers sample on Quest 3, and everything seems to work.