aboutsummaryrefslogtreecommitdiffhomepage
path: root/CMakeLists.txt
AgeCommit message (Collapse)Author
2023-03-15cmake: Minor CMake cleanupsdk-1.3.243.0sdk-1.3.243Juan Ramos
- Fix project name to be less confusing - Better testing
2023-02-22cmake: Update min to 3.15Juan Ramos
- Removes conditional 3.15 logic - Guarantees usage of --install/--loglevel
2023-01-30cmake: Trim CMakeLists.txtJuan Ramos
2023-01-19cmake: Update minimum to 3.14Juan Ramos
2023-01-11cmake: Cleanup vlk_get_header_version functionJuan Ramos
2023-01-11cmake: Removes unused CMake macrosJuan Ramos
2023-01-10cmake: Cleanup vlk_get_header_versionJuan Ramos
2023-01-09cmake: Remove Vulkan::RegistryJuan Ramos
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
2023-01-04docs: Update copyrightJuan Ramos
2022-12-20tests: Test Non-API headersJuan Ramos
Ensures the non-API headers compile correctly
2022-12-14cmake: Preserve permissions from registry filesJuan Ramos
2022-12-09cmake: Remove VULKAN_HEADERS_INSTALLJuan Ramos
Not needed and adds clutter to projects that use add_subdirectory
2022-12-09cmake: Cleanup CMake codeJuan Ramos
Remove version.cmake / install.cmake / cmake_uninstall.cmake Remove as much maintenace burden / custom code as possible
2022-11-10Fix duplicate quotes when targets are included by downstream projectsRyan Harrison
When trying to update the version of Vulkan-Headers used in Dawn/Tint, I encountered errors like this: Target "Vulkan-Headers" contains relative path in its INTERFACE_INCLUDE_DIRECTORIES: ""/home/foo/workspace/dawn/third_party/vulkan-deps/vulkan-headers/src/include"" This PR removes the offending quotes
2022-11-08cmake: Add VULKAN_HEADERS_INSTALL optionJuan Ramos
This allows projects which consume this repo with add_subdirectory to turn on/off the install logic, which can be undesirable.
2022-11-08cmake: Export CMake Targets FileJuan Ramos
Now as part of install 2 files are created: - VulkanHeadersConfig.cmake - VulkanHeadersConfigVersion.cmake This allows usage of find_package closes #157
2022-11-07cmake: Get Vulkan VersionJuan Ramos
Extract the vulkan header version for CMake usage
2022-11-04build: Fix CMake warningJuan Ramos
Currently GNUInstallDirs is complaining because no language has been enabled. This is fixed by enabling the C language.
2021-04-13Add vk_video headers to CMake install targetMike Schuchardt
2020-04-23Revert "Export versioned targets for CMake"Mike Weiblen
This reverts commit 382bf3de06fc8c8961055afc37957fe65846c33b. Revert PR #110 https://github.com/KhronosGroup/Vulkan-Headers/pull/110
2020-04-16Export versioned targets for CMakeRahul Sheth
Generate VulkanHeadersConfig.cmake and version file and install them. To get the version information the header file vulkan_core.h is parsed. In client code one can use `find_package(VulkanHeaders)` and get the targets `Vulkan::Headers` and `Vulkan::Registry`. The following additional files are generated and installed by CMake: - VulkanHeadersConfig.cmake: searched for by find_package(VulkanHeaders) - VulkanHeadersConfigVersion.cmake: provides version numbers - VulkanHeadersTargets.cmake: CMake target definitions used by config file
2019-07-16build: Update cmake_minimum_required(VERSION 3.10.2)Mike Weiblen
Change-Id: I28c30bb941691738944b13da75bc07e6153c89ef
2019-02-28build: Define library targets for nested builds-sdk-1.1.101.0Nuno Subtil
Adds alias interface libraries Vulkan::Headers and Vulkan::Registry that export include paths. These are meant to be used by dependent projects in a nested build configuration to obtain the path to the Vulkan headers and registry directories. Change-Id: I0801f4a23ef654064c1b0878543cd48965954756
2018-12-03build: Fix install target pathNuno Subtil
Use CMAKE_CURRENT_SOURCE_DIR instead of CMAKE_SOURCE_DIR when defining the path for the source files to be installed. CMAKE_SOURCE_DIR always points at the directory containing the root CMakeLists.txt, while CMAKE_CURRENT_SOURCE_DIR points at the directory containing the current project's CMakeLists.txt. These are normally identical, except when another CMake project includes this project via add_subdirectory() --- in that case, CMAKE_CURRENT_SOURCE_DIR is the right variable to use when composing paths to files within the current project tree. Change-Id: I4bdcc3bf538e96c43ae5f4ff6758cf45992442e0
2018-09-07build: CMakeLists.txt cleanupMike Weiblen
A cleanup of the CMake file in this repo, for consistency with similar effort in other Vulkan repos. clarify setting Windows install prefix if needed project() : NONE = this project has no language toolchain requirement. update .cmake-format.py 0.4.1 reformat using cmake-format 0.4.1 Change-Id: Ic64b335676eb6b8bd8ffd1b0d8c5468a4239287c
2018-06-27build: Beautify cmake filesMike Weiblen
Add the formatter config file (.cmake-format.py) and run: cmake-format -i CMakeLists.txt
2018-06-27build: Insert copyright in cmake filesMike Weiblen
2018-06-12cmake: Prevent redefinition of uninstall targetKarl Schultz
Allows for this repo to be included as a submodule of another repo that defines its own uninstall target. The uninstall target is best defined at the top-level repo.
2018-05-30build: Add CMake files for install targetKarl Schultz