commit | 13a54b303fd84b9387e88e8d52ce1504d8fa3ca5 | [log] [tgz] |
---|---|---|
author | John Bauman <jbauman@google.com> | Tue Nov 01 16:22:45 2022 -0500 |
committer | CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 16 23:19:27 2022 +0000 |
tree | 19418422910835b153930eac588ec3f36591f241 | |
parent | 8fd89f276412f95ab804ad855908c0a6800aa9c4 [diff] |
Don't set VULKAN_HPP_NO_NODISCARD_WARNINGS Setting VULKAN_HPP_NO_NODISCARD_WARNINGS globally is a divergence from upstream and removes a potentially-valuable check. Clients should be updated to set VULKAN_HPP_NO_NODISCARD_WARNINGS if needed. Change-Id: Iec84ef2ed3ce84a298a22418a04b10e4fa8ff046 Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/Vulkan-Headers/+/750990 Fuchsia-Auto-Submit: John Bauman <jbauman@google.com> Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com> Reviewed-by: John Rosasco <rosasco@google.com>
Vulkan header files and API registry
As discussed in #222, the default branch of this repository is now ‘main’. This change should be largely transparent to repository users, since github rewrites many references to the old ‘master’ branch to ‘main’. However, if you have a checked-out local clone, you may wish to take the following steps as recommended by github:
git branch -m master main git fetch origin git branch -u origin/main main git remote set-head origin -a
The contents of this repository are largely obtained from other repositories and are collected, coordinated, and curated here.
If proposing changes to any file originating from a different repository, please propose such changes in that repository, rather than Vulkan-Headers. Files in this repository originate from:
As of the Vulkan-Docs 1.2.182 spec update, the Vulkan-Hpp headers have been split into multiple files. All of those files are now included in this repository.
Updates to the Vulkan-Headers
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.