openharmony/third_party_vulkan-headers
1
0
Fork 0
mirror of https://gitee.com/openharmony/third_party_vulkan-headers synced 2024-11-23 07:49:47 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
289 Commits 144 Branches 23 Tags 20 MiB
C++ 90.7%
C 7.8%
Python 1.4%
2d8f6a63ae
Go to file
li_zt 2d8f6a63ae Revert add partialrender vulkan api 
This reverts commit a7ca7b9979.
Signed-off-by: li_zt <lishutian1@huawei.com>
2023-11-25 10:37:13 +08:00
.github/ISSUE_TEMPLATE update tag v1.2.201->v1.3.231 from github 2023-03-03 09:28:08 +00:00
cmake Revert "Export versioned targets for CMake" 2020-04-23 10:59:45 -06:00
include Revert add partialrender vulkan api 2023-11-25 10:37:13 +08:00
registry standardize OH extension api 2023-06-19 11:39:31 +08:00
.cmake-format.py build: CMakeLists.txt cleanup 2018-09-07 13:51:11 -06:00
.gitattributes repo: Add .gitattributes file 2018-09-07 13:45:38 -06:00
.gitignore repo: Add to vim temp files to .gitignore 2018-09-07 13:48:52 -06:00
BUILD.gn standardize OH extension api 2023-06-19 11:39:31 +08:00
BUILD.md build: Clarify Windows build instructions 2019-11-21 12:00:19 -07:00
bundle.json add bundle.json 2023-08-17 15:31:50 +08:00
CMakeLists.txt Add vk_video headers to CMake install target 2021-04-13 16:23:52 -07:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2018-10-10 16:06:12 -04:00
LICENSE.txt Revert LICENSE to Apache 2.0 2018-10-03 10:16:17 -04:00
OAT.xml fix OAT 2022-11-17 06:40:55 +00:00
README_OpenHarmony.md standardize OH extension api 2023-06-19 11:39:31 +08:00
README.md update tag v1.2.201->v1.3.231 from github 2023-03-03 09:28:08 +00:00
README.OpenSource add ohos ext base on v1.3.231 2023-03-03 10:04:49 +00:00

README.md

Vulkan-Headers

Vulkan header files and API registry

Default branch changed to 'main' 2021-09-12

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

Repository Content

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/cgenerator.py
  • registry/spec_tools/conventions.py
  • registry/generator.py
  • registry/genvk.py
  • registry/reg.py
  • registry/spec_tools/util.py
  • registry/validusage.json
  • registry/video.xml
  • registry/vk.xml
  • registry/vkconventions.py
  • All files under include/vulkan/ which are not listed explicitly as originating from another repository.

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

  • .cmake-format.py
  • BUILD.gn
  • BUILD.md
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
  • LICENSE.txt
  • README.md
  • cmake/Copyright_cmake.txt
  • cmake/cmake_uninstall.cmake.in
  • Non-API headers (report issues to the Vulkan-Loader/issues tracker)
    • 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/vulkan.hpp
  • include/vulkan/vulkan_enums.hpp
  • include/vulkan/vulkan_funcs.hpp
  • include/vulkan/vulkan_handles.hpp
  • include/vulkan/vulkan_raii.hpp
  • include/vulkan/vulkan_structs.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.