Prototype of RAW decoding in Skia.

DEPS

Index: DEPS
diff --git a/DEPS b/DEPS
index a76953d31df6aedbdb32e9f3eb451c6afc16f44e..cb3ffe94342b624d4ccdea1815ac512ae3997cfc 100644
--- a/DEPS
+++ b/DEPS
@@ -22,6 +22,9 @@ deps = {
   "third_party/externals/libpng"  : "https://skia.googlesource.com/third_party/libpng.git@070a616b8275277e18ef8ee91e2ca23f7bdc67d5",
   "third_party/externals/giflib"  : "https://android.googlesource.com/platform/external/giflib.git@ab10e256df4f684260ca239905b1cec727181f6c",
 
+  "third_party/externals/dng_sdk" : "https://android.googlesource.com/platform/external/dng_sdk.git@master",

[scroggo, 2016/01/21 16:36:10]

I just realized that this points to a branch rather than a particular commit or
tag. All of our other DEPS use a particular tag. Sticking with a particular
commit or tag has the downside of meaning that we need to change this file to
get new commits (e.g. your fix for mac), but it also means things won't suddenly
(and mysteriously, to a Skia developer) stop working if someone changed
upstream. For example, if someone landed a change in upstream that required a
makefile change, we need to update our gyp file. But if we silently get the new
version, it will take some extra work (for someone who probably isn't familiar
with the library) to figure out what gyp file changes are necessary.

Anyway, please specify the commit to use for both libraries.

[yujieqin, 2016/01/21 17:44:26]

Thanks for the tips. It makes sense. :)

+  "third_party/externals/piex"    : "https://android.googlesource.com/platform/external/piex.git@master",
+
   "third_party/externals/libjpeg-turbo"             : "https://skia.googlesource.com/third_party/libjpeg-turbo.git@36422d9e165a33914436068536772cc6ed1e7886",
   # libjpeg-turbo depends on yasm to compile .asm files
   "third_party/externals/yasm/source/patched-yasm/" : "https://chromium.googlesource.com/chromium/deps/yasm/patched-yasm.git@4671120cd8558ce62ee8672ebf3eb6f5216f909b",