5eeb2c4c57
Vulkan::Registry behaves differently in `add_subdirectory` vs `find_package` builds. Which can result in build failures. Also Vulkan::Registry never made sense as a CMake target and was very brittle in numerous ways. Better to provide a `VULKAN_HEADERS_REGISTRY_DIRECTORY` to users instead and remove Vulkan::Registry completely. closes #351
Vulkan-Headers
Vulkan header files and API registry
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/*.py
- registry/spec_tools/*.py
- registry/profiles/*.json
- All files under include/vulkan/ which are not listed explicitly as originating from another repository.
This repository (https://github.com/KhronosGroup/Vulkan-Headers)
- BUILD.gn
- BUILD.md
- cmake/
- CMakeLists.txt
- tests/*
- CODE_OF_CONDUCT.md
- INTEGRATION.md
- LICENSE.txt
- README.md
- Non-API headers
- 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)
As of the Vulkan-Docs 1.2.182 spec update, the Vulkan-Hpp headers have been split into multiple files. All of those files are now included in this repository.
- include/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.