Clone this repo:
  1. facac95 build: Update to header 1.3.229 by Mike Schuchardt · 2 years, 10 months ago master v1.3.229
  2. 5b4f221 build: Update to header 1.3.228 by Mike Schuchardt · 2 years, 10 months ago v1.3.228
  3. f7dff1f build: Update to header 1.3.227 by Mike Schuchardt · 2 years, 10 months ago v1.3.227
  4. d9f4641 build: Also include XCB header path by Brad Smith · 2 years, 10 months ago
  5. 1ef7bc1 Move BUILD.gn values into the scope that uses them by Brandon Jones · 2 years, 11 months ago

Vulkan Ecosystem Components

This project provides Khronos official Vulkan Tools and Utilities for Windows, Linux, Android, and MacOS.

CI Build Status

Build Status

Introduction

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:

Contact Information

Information for Developing or Contributing:

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.

How to Build and Run

BUILD.md Includes directions for building all components as well as running the vkcube demo applications.

Version Tagging Scheme

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.

License

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.

Acknowledgements

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.