Assiduous

This requires [Ubuntu22](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2204-Readme.md) which is Beta so far.

Ubuntu 22 is in Beta on GitHub actions, so clang and gcc versions have not been updated on CI. Diligent should still compile fine with clang 14 and gcc 12.

Hi! Thanks for looking into this. I am not very familiar with OpenXR, so please correct me where I am wrong. From my understanding, from the graphics point of view...

@mathisloge Thanks for looking into this. First of all, few notes about why things are the way they currently are: Diligent depends on multiple third-party projects, which we integrate as...

> As a result, every dependency is considered an external dependency and must be based on the finding mechanism of cmake. Is my understanding correct that basically vcpkg is a...

OK, things are a bit more clearer now. Since code stability and quality is paramount for us, we can't switch the main build system to the one where dependencies are...

> I've added a CMake option DILIGENT_USE_BUNDLED_DEPENDENCIES which defaults to ON. So when DILIGENT_USE_BUNDLED_DEPENDENCIES=ON the submodules are used. if DILIGENT_USE_BUNDLED_DEPENDENCIES=OFF a cmake file is included, which has all those find_package...

@mathisloge I updated core, tools and samples to allow their dependencies to be provided externally. If required targets already exist, Diligent will use those instead of the bundled - nothing...

@mathisloge I committed a bunch of updates: * Core: use `volk` and `GLEW::GLEW` * Tools: use `JPEG::JPEG`, `TIFF::TIFF`, `PNG::PNG`, and `ZLIB::ZLIB` > So to support those find_package calls I'm proposing...

> for vcpkg I need to make seperate targets, since it is discouraged to add submodules to ports. so there will be diligent-core, diligent-tools, diligent-fx Are they going to be...