97caefd055
I had to copy some config_settings out of //bazel/common_config_settings because these are now treated as separate entities and cannot see that file. For libpng, note that we use a genrule to create the pnglibconf.h instead of pointing to one somewhere else. This ended up being easier than other things I tried. Another approach would be to not depend on the version in third_party/externals, but to clone it via new_git_repository [1] and apply a patch that creates the configuration file. [1] https://bazel.build/rules/lib/repo/git#new_git_repository Bug: skia:12541 Change-Id: I9a284775dc0f2bdabb145518d5f0803c74fb99fa Reviewed-on: https://skia-review.googlesource.com/c/skia/+/545368 Reviewed-by: Ben Wagner <bungeman@google.com> |
||
---|---|---|
.. | ||
angle2 | ||
brotli | ||
cpu-features | ||
d3d12allocator | ||
dng_sdk | ||
etc1 | ||
expat | ||
freetype2 | ||
harfbuzz | ||
highway | ||
icu | ||
imgui | ||
libjpeg-turbo | ||
libjxl | ||
libmicrohttpd | ||
libpng | ||
libwebp | ||
lua | ||
native_app_glue | ||
oboe | ||
piex | ||
rive | ||
sfntly | ||
skcms | ||
spirv-cross | ||
vulkanmemoryallocator | ||
wuffs | ||
zlib | ||
BUILD.bazel | ||
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.