commit | 183d98b488a32b2185919600ad2239cbb6e25d7c | [log] [tgz] |
---|---|---|
author | Jeremy Kniager <jeremyk@lunarg.com> | Fri Mar 27 09:24:47 2020 -0600 |
committer | jeremyk-lunarg <jeremyk@lunarg.com> | Mon Mar 30 08:23:05 2020 -0600 |
tree | a6b1dd0eef01c18e113bbbb2d5bd8a11c4478166 | |
parent | a860d5d519bbf2f8d518235c4badbb614198eb08 [diff] |
travis: Add clang-format verions output to travis Updated `.travis.yml` to output the clang-format version before running a clang-format check. Updated `check_code_format.sh` to include a suggestion to check the user's clang-format version if an error occures. Change-Id: I4328350cedb27998bd84a3d675eab51c89fb1a9e
This project provides Khronos official Vulkan Tools and Utilities for Windows, Linux, Android, and MacOS.
Platform | Build Status |
---|---|
Linux/Android | |
Windows |
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:
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 the vkcube demo applications.
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.
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.
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.