| commit | 07855244f40e6e4bc244e0c97c81e41ab532fc9a | [log] [tgz] |
|---|---|---|
| author | Victor Khimenko <[email protected]> | Tue Jun 25 19:18:40 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Jun 25 19:18:40 2024 +0000 |
| tree | 648095e18a224a829e0fc16575631549a472079f | |
| parent | 516f051153fe3db5899dbc926e8be9875f4f8aeb [diff] | |
| parent | 1356b36749749738ad35b70c4e01606d07afc04a [diff] |
Add emulated_apit_checker for Vulkan am: 1356b36749 Original change: https://android-review.googlesource.com/c/platform/external/vulkan-headers/+/3140820 Change-Id: Ie7163a0640c6b708b746c855cf0af583b1e476f7 Signed-off-by: Automerger Merge Worker <[email protected]>
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.
See the CONTRIBUTING.md
See BUILD.md
Vulkan-Headers are shipped as part of the official Vulkan-SDK
Vulkan-Headers are also supported by both conan & vcpkg.
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.