Google Git
Sign in
fuchsia / third_party / Vulkan-Headers / b232cb2bee65308b0ffbd7439635121b145502ff
commitb232cb2bee65308b0ffbd7439635121b145502ff[log] [tgz]
authorJuan Ramos <juan@lunarg.com>Tue Dec 27 12:20:23 2022 -0700
committerJuan Ramos <114601453+juan-lunarg@users.noreply.github.com>Tue Dec 27 12:27:55 2022 -0700
treeb60a892efbc1353bf0d3c59c1880d606f71616c8
parentfc90b60663965aec582d5bf7965f4e6b15173730 [diff]
cxx: Use pragma once consistently for non-api headers
3 files changed
tree: b60a892efbc1353bf0d3c59c1880d606f71616c8
  1. .github/
  2. include/
  3. registry/
  4. tests/
  5. .gitattributes
  6. .gitignore
  7. BUILD.gn
  8. BUILD.md
  9. CMakeLists.txt
  10. CODE_OF_CONDUCT.md
  11. INTEGRATION.md
  12. LICENSE.txt
  13. README.md
README.md

Vulkan-Headers

Vulkan header files and API registry

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:

Specification repository (https://github.com/KhronosGroup/Vulkan-Docs)

  • registry/*.py
  • registry/spec_tools/*.py
  • registry/profiles/*.json
  • All files under include/vulkan/ which are not listed explicitly as originating from another repository.

This repository (https://github.com/KhronosGroup/Vulkan-Headers)

  • BUILD.gn
  • BUILD.md
  • CMakeLists.txt
  • tests/*
  • CODE_OF_CONDUCT.md
  • INTEGRATION.md
  • LICENSE.txt
  • README.md
  • Non-API headers
    • include/vulkan/vk_icd.h
    • include/vulkan/vk_layer.h
    • include/vulkan/vk_sdk_platform.h

Vulkan C++ Binding Repository (https://github.com/KhronosGroup/Vulkan-Hpp)

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.

  • include/vulkan/*.hpp

Version Tagging Scheme

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.