25b392329f
https://skia.googlesource.com/skcms.git/+log/4f7135f89d98..c1e907c8f007 2021-09-01 rmistry@google.com Use repo-specific tree_status_url in skcms If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skcms-skia-autoroll Please CC fmalita@google.com,brianosman@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Skia: https://bugs.chromium.org/p/skia/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: skia/skia.primary:Canary-Chromium Tbr: fmalita@google.com,brianosman@google.com Change-Id: Ifdafe51d96ebb0b3dd2fa4ddda273ae9375c6ff8 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/444700 Reviewed-by: skia-autoroll <skia-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: skia-autoroll <skia-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: skia-autoroll <skia-autoroll@skia-public.iam.gserviceaccount.com> |
||
|---|---|---|
| .. | ||
| angle2 | ||
| brotli | ||
| cpu-features | ||
| d3d12allocator | ||
| dng_sdk | ||
| etc1 | ||
| expat | ||
| freetype2 | ||
| harfbuzz | ||
| icu | ||
| imgui | ||
| libjpeg-turbo | ||
| libmicrohttpd | ||
| libpng | ||
| libwebp | ||
| lua | ||
| native_app_glue | ||
| oboe | ||
| piex | ||
| sfntly | ||
| skcms | ||
| spirv-cross | ||
| 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.