commit | 203572ccdb2bd105b5627de6b877a437cb599a4c | [log] [tgz] |
---|---|---|
author | John Bauman <jbauman@google.com> | Tue Dec 08 00:06:11 2020 +0000 |
committer | John Bauman <jbauman@google.com> | Tue Dec 08 18:11:30 2020 +0000 |
tree | f7231f87c29583e29299b43bac581b81951d3d4f | |
parent | e0530c262ebc8f43c622c8c9728bf7a6c0ac33b6 [diff] |
Convert vkcube to use .cmx shard Including this shard helps ensure all applications provide the correct set of services to the Vulkan driver. Bug: 64508 Change-Id: I7ee234ee82a39fc790e1aaffab6c3dce2f15e1eb Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/Vulkan-Tools/+/458397 Reviewed-by: Craig Stout <cstout@google.com>
This project provides Khronos official Vulkan Tools and Utilities for Windows, Linux, Android, and MacOS.
Platform | Build Status |
---|---|
Linux/Android | |
Windows |
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 COPYRIGHT.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.