commit | 9439e17f9739496e49fdd8f274e15d32d1785bc3 | [log] [tgz] |
---|---|---|
author | Yilong Li <liyl@google.com> | Wed Nov 04 19:56:33 2020 -0800 |
committer | Yilong Li <liyl@google.com> | Thu Nov 05 21:52:47 2020 +0000 |
tree | 5b3e3ddc80de263c3ba81ee2dcaf23f1ee47d499 | |
parent | 5933f0b2c66017af27de3aeecc475dc2281d9f1c [diff] |
build: Allow generating layers json file for cross-compiling Upstream change: https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/2302 This change is the same as upstream change except that it adds Fuchsia specific BUILD.gn modification. ---------------------------------- `generate_vulkan_layers_json.py` generates validation layer description JSON file where the layer library file name is determined by the host system type. However, for Fuchsia cross-compiling this doesn't work. Instead, we need to specify the target platform type explicitly in the script. This change adds an optional argument `--platform Linux|Darwin| Windows|...` to `generate_vulkan_layers_json.py`, so that it could generate layers json file with correct library filename for specific target platforms. It is useful when making cross-platform builds. Test: Run `generate_vulkan_layers_json.py` 1) without `--platform` argument, 2) with `--platform Windows`, 3) with `--platform Linux`, 4) `--platform Darwin` and 5) with `--platform Fuchsia`. Verification: - Run "fx set workstation.x64; fx build" on macOS. - Verified that out/default/vulkan_layers_data/ VkLayer_khronos_validation.json uses "VkLayer_khronos_validation.so" as library file name. Bug: 63670 Change-Id: If0ae9571e9b82c78b1caef7c5ac116ef31270999 Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/Vulkan-ValidationLayers/+/447334 Reviewed-by: John Rosasco <rosasco@google.com> Reviewed-by: Yilong Li <liyl@google.com>
This project provides the Khronos official Vulkan validation layers for Windows, Linux, Android, and MacOS.
Platform | Build Status |
---|---|
Linux/Android | |
Windows |
Vulkan is an Explicit API, enabling direct control over how GPUs actually work. By design, minimal error checking is done inside a Vulkan driver. Applications have full control and responsibility for correct operation. Any errors in how Vulkan is used can result in a crash. This project provides Vulkan validation layers that can be enabled to 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 validation tests.
Information on how to enable the various Validation layers is in LAYER_CONFIGURATION.md.
Updates to the Vulkan-ValidationLayers
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.