skia2/third_party
Mike Klein 085bc52363 write -isystem paths relative to the build root
The default makes these system-absolute paths,
which confuses fiddle's overlay builds.

Now we should see things like,

  -isystem ../third_party/externals/jsoncpp/include

where we previously had,

  -isystem /Users/mtklein/skia/third_party/externals/jsoncpp/include

Change-Id: I7b161a550fdb95b06e17c372cd5bec3015e3c8b7
Reviewed-on: https://skia-review.googlesource.com/109382
Reviewed-by: Joe Gregorio <jcgregorio@google.com>
Commit-Queue: Mike Klein <mtklein@chromium.org>
2018-02-22 16:06:32 +00:00
..
angle2 Fix Angle autoroller by adding missing platform specific files. 2018-02-21 22:18:07 +00:00
cpu-features
dng_sdk remove mips support and bots 2017-12-05 17:19:45 +00:00
expat
freetype/include/freetype-android
freetype2
gif Remove unused field/methods 2018-01-25 01:04:13 +00:00
googletest GPU-CTS Program 2017-10-17 19:01:13 +00:00
harfbuzz
icu Build ICU on iOS 2018-02-12 15:51:01 +00:00
imgui
jsoncpp
libjpeg-turbo Update to the latest version of libjpeg-turbo 2017-12-07 13:15:20 +00:00
libmicrohttpd
libpng roll libpng to 1.6.33 2017-10-02 17:31:34 +00:00
libsdl Add iOS support for SkiaSDLExample. 2017-08-30 18:56:46 +00:00
libwebp Roll libwebp to 0.6.1 2018-02-14 19:00:27 +00:00
lua avoid using tmpnam() in Lua 2018-02-01 22:39:59 +00:00
native_app_glue
piex
sfntly
skcms add basic skia -> skcms dependency 2018-01-26 02:07:37 +00:00
spirv-headers
spirv-tools corrected spirv tools output file name 2017-09-25 13:28:29 +00:00
vulkan/vulkan
zlib
BUILD.gn
README
third_party.gni write -isystem paths relative to the build root 2018-02-22 16:06:32 +00:00

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.