| commit | 520163b4b3f3f6e4696a6355f029d9e05d3bb9cf | [log] [tgz] |
|---|---|---|
| author | Charles Giessen <charles@lunarg.com> | Mon Sep 18 22:24:49 2023 -0600 |
| committer | Juan Ramos <114601453+juan-lunarg@users.noreply.github.com> | Fri Sep 22 16:30:39 2023 -0600 |
| tree | d9c62afd9ec3d3e9c4dadc08388c7f4200383f78 | |
| parent | c92c1e0654045eccca6a7f2559102d5264ee938f [diff] |
icd: Add VkPhysicalDeviceDriverProperties This commit adds support for the VkPhysicalDeviceDriverProperties struct in the output of vkGetPhysicalDeviceProperties2. This is useful for users of Mock ICD wishing to know the version of MockICD used. The driverInfo field is used for this purpose and contains the git branch & tag info data. The use of Git in CMake is how the information is seamlessly gotten and provided to the source code in the form of compile definitions.
This project provides Vulkan tools and utilities that can assist development by enabling developers to verify their applications correct use of the Vulkan API.
The following components are available in this repository:
Please see the CONTRIBUTING.md file in this repository for more details. Please see the GOVERNANCE.md file in this repository for repository management details.
BUILD.md includes directions for building all components as well as running the vkcube demo applications.
Updates to the Vulkan-Tools 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.
This work is released as open source under a Apache-style license from Khronos including a Khronos copyright.
See LICENSE.txt for a full list of licenses used in this repository.
While this project has been developed primarily by LunarG, Inc., there are many other companies and individuals making this possible: Valve Corporation, funding project development; Google providing significant contributions to the validation layers; Khronos providing oversight and hosting of the project.