aboutsummaryrefslogtreecommitdiffhomepage
path: root/BUILD.md
diff options
context:
space:
mode:
authorJuan Ramos <[email protected]>2023-01-09 16:12:28 -0700
committerJuan Ramos <[email protected]>2023-01-09 17:01:08 -0700
commit5eeb2c4c570ce92f5f48bf667e39e9d4da2ef13a (patch)
treeadeb1a96431a93c8717315b813e315ef7c6a5f25 /BUILD.md
parent18963a6cc03fe15e3785d353dea6a1ff95115a5e (diff)
downloadVulkan-Headers-5eeb2c4c570ce92f5f48bf667e39e9d4da2ef13a.tar.gz
Vulkan-Headers-5eeb2c4c570ce92f5f48bf667e39e9d4da2ef13a.zip
cmake: Remove Vulkan::Registry
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
Diffstat (limited to 'BUILD.md')
-rw-r--r--BUILD.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/BUILD.md b/BUILD.md
index 03d6b7c..913208c 100644
--- a/BUILD.md
+++ b/BUILD.md
@@ -54,6 +54,8 @@ Which, when successful, will add library target called `Vulkan::Headers` which y
find_package(VulkanHeaders REQUIRED CONFIG)
target_link_libraries(foobar PRIVATE Vulkan::Headers)
+
+message(STATUS "Vulkan Headers Registry: ${VULKAN_HEADERS_REGISTRY_DIRECTORY}")
```
## Repository Set-Up