21706f1d14
Bug: chromium:922430 Bug: b/135180511 Chromium has diverged from upstream libjpeg-turbo in order to take advantage of SIMD optimizations that have not yet been merged into upstream. Android is also interested in using these. Switch to the version with the optimizations in order to test them. Chromium has its own jconfig.h and jconfigint.h, so ours are never used after the switch. Remove them. The only Skia-specific modification to these files was to define flags to enable arithmetic encoding. Move them to BUILD.gn, so they're still applied. Also remove jsimdcfg.inc, which is currently unused. (It appears to be only for x86/x64, where we are not building SIMD anyway.) Update BUILD.gn to build SIMD files on arm. The existing ones have moved, and there are new ones to build, too. Change-Id: I47606609c23be43b319150ffb5a4fe55d8869755 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/311105 Commit-Queue: Leon Scroggins <scroggo@google.com> Reviewed-by: Mike Klein <mtklein@google.com> Reviewed-by: Eric Boren <borenet@google.com> |
||
|---|---|---|
| .. | ||
| angle2 | ||
| cpu-features | ||
| dng_sdk | ||
| etc1 | ||
| expat | ||
| freetype2 | ||
| glslang | ||
| harfbuzz | ||
| icu | ||
| imgui | ||
| libjpeg-turbo | ||
| libmicrohttpd | ||
| libpng | ||
| libsdl | ||
| libwebp | ||
| lua | ||
| native_app_glue | ||
| opencl | ||
| piex | ||
| sfntly | ||
| shaderc | ||
| skcms | ||
| spirv-cross | ||
| spirv-headers | ||
| spirv-tools | ||
| 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.