fb33355c36
This rolls skcms into skia and builds it in dev configurations. We don't use it in any way yet, but if nothing else this gives us roundabout Windows skcms build bots. Bug: skia:7493 Change-Id: Idd945ccd5c7a543841d76ab600cc117f2ee074dc Reviewed-on: https://skia-review.googlesource.com/99880 Reviewed-by: Mike Klein <mtklein@chromium.org> Commit-Queue: Mike Klein <mtklein@chromium.org> |
||
---|---|---|
.. | ||
angle2 | ||
cpu-features | ||
dng_sdk | ||
etc1 | ||
expat | ||
freetype/include/freetype-android | ||
freetype2 | ||
gif | ||
googletest | ||
harfbuzz | ||
icu | ||
imgui | ||
jsoncpp | ||
libjpeg-turbo | ||
libmicrohttpd | ||
libpng | ||
libsdl | ||
libwebp | ||
lua | ||
native_app_glue | ||
piex | ||
sfntly | ||
skcms | ||
spirv-headers | ||
spirv-tools | ||
vulkan/vulkan | ||
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.