[automerger skipped] Add VK_GOOGLE_surfaceless_query am: 28dc168c2f -s ours

am skip reason: Merged-In I1df97ff7471dd6f98e9f7dbd138e6a9096cfc10a with SHA-1 1df8aa7265 is already in history

Original change: https://android-review.googlesource.com/c/platform/external/vulkan-headers/+/2022116

Change-Id: If75897caa29578bf5e09ad992cf1eff35be88f3d
tree: 1f99bbdc2a1a2cdbf13ae5953d9af0e3af14160c
  1. cmake/
  2. include/
  3. registry/
  4. .cmake-format.py
  5. .gitattributes
  6. .gitignore
  7. Android.bp
  8. BUILD.gn
  9. BUILD.md
  10. CMakeLists.txt
  11. CODE_OF_CONDUCT.md
  12. LICENSE.txt
  13. METADATA
  14. OWNERS
  15. README.md
README.md

Vulkan-Headers

Vulkan header files and API registry

Repository Content

The contents of this repository are largely obtained from other repositories and are collected, coordinated, and curated here.

If proposing changes to any file originating from a different repository, please propose such changes in that repository, rather than Vulkan-Headers. Files in this repository originate from:

Specification repository (https://github.com/KhronosGroup/Vulkan-Docs)

  • registry/cgenerator.py
  • registry/conventions.py
  • registry/generator.py
  • registry/genvk.py
  • registry/reg.py
  • registry/spec_tools/util.py
  • registry/validusage.json
  • registry/vk.xml
  • registry/vkconventions.py
  • All files under include/vulkan/ which are not listed explicitly as originating from another repository.

This repository (https://github.com/KhronosGroup/Vulkan-Headers)

  • .cmake-format.py
  • BUILD.gn
  • BUILD.md
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
  • LICENSE.txt
  • README.md
  • cmake/Copyright_cmake.txt
  • cmake/cmake_uninstall.cmake.in
  • Non-API headers (report issues against @lenny-lunarg)
    • include/vulkan/vk_icd.h
    • include/vulkan/vk_layer.h
    • include/vulkan/vk_sdk_platform.h

Vulkan C++ Binding Repository (https://github.com/KhronosGroup/Vulkan-Hpp)

  • include/vulkan/vulkan.hpp

Version Tagging Scheme

Updates to the Vulkan-Headers repository which correspond to a new Vulkan specification release are tagged using the following format: v<version> (e.g., v1.1.96).

Note: Marked version releases have undergone thorough testing but do not imply the same quality level as SDK tags. SDK tags follow the sdk-<version>.<patch> format (e.g., sdk-1.1.92.0).

This scheme was adopted following the 1.1.96 Vulkan specification release.