[readme_fuchsia] Remove duplicate README.fuchsia file

In the fuchsia tree, the correct one will be located one folder up.

Change-Id: I13d69f1dad636c5753a7ce9544db000b6ef3218f
Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/Vulkan-Tools/+/1830209
Reviewed-by: Jiaming Li <lijiaming@google.com>
Commit-Queue: Jerry Belton <jcecil@google.com>
1 file changed
tree: 6ca61ba579eedd810873f8911dd212a48991d3a8
  1. .github/
  2. cube/
  3. icd/
  4. scripts/
  5. tests/
  6. vulkaninfo/
  7. .clang-format
  8. .gitattributes
  9. .gitignore
  10. BUILD.gn
  11. BUILD.md
  12. CMakeLists.txt
  13. CODE_OF_CONDUCT.md
  14. CONTRIBUTING.md
  15. GOVERNANCE.md
  16. LICENSE.txt
  17. OWNERS
  18. README.md
README.md

KhronosGroup/Vulkan-Tools

This project provides Vulkan tools and utilities that can assist development by enabling developers to verify their applications correct use of the Vulkan API.

Intro

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 this repository which correspond to a new Vulkan specification release are tagged using the following format: v<version> (e.g., v1.3.266).

Note: Marked version releases have undergone thorough testing but do not imply the same quality level as SDK tags. SDK tags follow the vulkan-sdk-<version>.<patch> format (e.g., vulkan-sdk-1.3.266.0).

This scheme was adopted following the 1.3.266 Vulkan specification release.

License

This work is released as open source under a Apache-style license from Khronos including a Khronos copyright.

See LICENSE.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.