Google Git
Sign in
android / platform / external / vulkan-headers / 5ac36269f50381bdd92a5e1973d8eb041771e59e
commit5ac36269f50381bdd92a5e1973d8eb041771e59e[log] [tgz]
authorunknown <charles@lunarg.com>Fri Feb 09 10:05:03 2024 -0600
committerCharles Giessen <46324611+charles-lunarg@users.noreply.github.com>Fri Feb 09 08:18:46 2024 -0800
tree49376dfdfa77b7497720f524d7698cf636f9af41
parent5a5c9a643484d888873e32c5d7d484fae8e71d3d [diff]
build: Update build.gn with AV1 headers

av1std_decode.h & av1std.h were added recently and needed adding to the
build.gn build.
1 file changed
tree: 49376dfdfa77b7497720f524d7698cf636f9af41
  1. .github/
  2. .reuse/
  3. include/
  4. LICENSES/
  5. registry/
  6. tests/
  7. .gitattributes
  8. .gitignore
  9. BUILD.gn
  10. BUILD.md
  11. CMakeLists.txt
  12. CODE_OF_CONDUCT.adoc
  13. CONTRIBUTING.md
  14. LICENSE.md
  15. README.md
  16. SECURITY.md
README.md

Vulkan-Headers

Vulkan header files and API registry

This repository contains Vulkan header files, include files for C and C++, and related scripts and tests.

Most of the files in this repository are sourced from, or generated from, other repositories as described in CONTRIBUTING.md. Vulkan-Headers exists as a staging area for these files, most of which are then consumed by downstream repositories used to build SDK components such as the Vulkan Validation Layers and Conformance Test Suite.

Developers normally obtain headers from the official Vulkan-SDK. They can also use headers from, or packaged from, this repository.

In most cases, developers should only need the headers, not the scripts and other material in this repository. If you need to run the scripts, please use them from their canonical source in the Vulkan Specification repository.

Contributing

See the CONTRIBUTING.md

Building

See BUILD.md

SDK Support

Vulkan-Headers are shipped as part of the official Vulkan-SDK

C/C++ Package Manager Support

Vulkan-Headers are also supported by both conan & vcpkg.

Version Tagging Scheme

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

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

This scheme was adopted following the 1.3.266 Vulkan specification release.