b733320ab1
These aren't currently being used. Our clients typically compile libjpeg-turbo themselves and use their own yasm to build the .asm files. For the libjpeg-turbo that we use to test, we don't compile the .asm optimizations. Maybe we should do this... But while we don't there is no need for the yasm config files. BUG=skia: Change-Id: I903a47ce444b6740b32fe8d99472c4d959058f7b Reviewed-on: https://skia-review.googlesource.com/9238 Commit-Queue: Mike Klein <mtklein@chromium.org> Reviewed-by: Mike Klein <mtklein@chromium.org> |
||
|---|---|---|
| .. | ||
| angle2 | ||
| cpu-features | ||
| dng_sdk | ||
| etc1 | ||
| expat | ||
| freetype/include/freetype-android | ||
| freetype2 | ||
| gif | ||
| harfbuzz | ||
| icu | ||
| imgui | ||
| jsoncpp | ||
| libjpeg-turbo | ||
| libmicrohttpd | ||
| libpng | ||
| libsdl | ||
| libwebp | ||
| lua | ||
| native_app_glue | ||
| piex | ||
| sfntly | ||
| 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.