v1.2.0 release

• revamped action into a consolidated CMakeLists.txt approach.
  • in part this was to leverage cmake's ExternalProject_Add functionality, which simplifies "calling out" into the various dependent Khronos repos that basically standardize around cmake already.
• added support for building individual SDK components:
  • Vulkan-Headers
  • Vulkan-Loader
  • Glslang
  • SPIRV-Cross
  • SPIRV-Tools
  • SPIRV-Reflect
  • SPIRV-Headers
• eliminated unnecessary changes to the host project build environment
  • previously building SDK components could end up "polluting" the host project environment on windows (ie: the ninja version that building SDK components themselves depends on becoming the default ninja seen in the PATH)
  • on windows this action now uses humbletim/vsdevenv-shell to very selectively enable build tools for specific internal steps, while leaving the host project environment as unaffected as practical
• now works with the upcoming windows-2022 github actions environment (which will become windows-latest at some point in the future)

v1.0.3

• improved Windows cmd and powershell compatibility:
  • VULKAN_SDK now uses mixed-style paths (eg: d:/sub/dir as opposed to /d/sub/dir)
  • appears to fix #4 -- kudos to @Wunkolo for the bug report and $(pwd -W) suggestion!
• added a simple vulkan C test program + CMake build to this repo's local CI
  • this helps automatically verify end-to-end SDK installation and VULKAN_SDK use across varying github action scenarios (see ci.yml)

v1.0.2

• added verbose output if a specified Vulkan SDK release number fails to resolve
• (advanced) added support for using Vulkan SDK internal branch names (eg: sdk-1.1.101)
  • note: using a full release number is still recommended because then the built SDK will correspond 1:1 with an official release point
  • however, using an internal branch may be more reliable because it avoids the need to query SDK webservices

v1.0.1

initial marketplace release

v1

update actions path