54bfb18dad
This should allow clients to include Skia and their vulkan files in any order. However, it does require that when clients are building their files that include skia with vulkan, they must have vulkan/vulkan_core.h on their include path somewhere. Bug: skia: Change-Id: I969db396c92127be7c8df754926d175f38b8aafa Reviewed-on: https://skia-review.googlesource.com/c/172147 Reviewed-by: Brian Salomon <bsalomon@google.com> Commit-Queue: Greg Daniel <egdaniel@google.com> |
||
---|---|---|
.. | ||
angle2 | ||
cpu-features | ||
dng_sdk | ||
expat | ||
freetype2 | ||
gif | ||
googletest | ||
harfbuzz | ||
icu | ||
imgui | ||
jsoncpp | ||
libjpeg-turbo | ||
libmicrohttpd | ||
libpng | ||
libsdl | ||
libwebp | ||
lua | ||
native_app_glue | ||
Nima-Cpp | ||
piex | ||
sfntly | ||
skcms | ||
spirv-headers | ||
spirv-tools | ||
vulkan | ||
vulkanmemoryallocator | ||
wuffs | ||
zlib | ||
BUILD.gn | ||
README | ||
third_party.gni |
The third_party directory contains a set of dependencies from outside sources that are needed to build various components and tools within Skia. Some of these dependencies reside within the Skia repo, while others are pulled from other repositories and placed in the third_party/externals directory during build. These external dependencies are defined in a DEPS file. Products in third_party are subject to their own respective license terms. The license for each project should be included in the source itself via a license header or file. If the source itself does not include a license header or file, create a README that refers to reliable documentation of the project's license terms on the web.