summaryrefslogtreecommitdiffstats
path: root/ppapi/c/DEPS
diff options
context:
space:
mode:
authordmichael@chromium.org <dmichael@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-12-01 20:12:37 +0000
committerdmichael@chromium.org <dmichael@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-12-01 20:12:37 +0000
commit2059f3d1c2e72d67797567c733dd6377ad5aceff (patch)
tree12df83060885af18ea09879aa85cff3f3b04979f /ppapi/c/DEPS
parent0090bc2f8f7077df2721c457f620890e627c204a (diff)
downloadchromium_src-2059f3d1c2e72d67797567c733dd6377ad5aceff.zip
chromium_src-2059f3d1c2e72d67797567c733dd6377ad5aceff.tar.gz
chromium_src-2059f3d1c2e72d67797567c733dd6377ad5aceff.tar.bz2
Add DEPS include rules so we don't accidentally use chromium stuff.
I basically turned off everything that is turned on in the root DEPS file, and then selectively turned stuff on. I had to provide some macros to replace the use of base/compilerspecific.h and build/buildconfig.h. I'm not sure if we have a coherent understanding of private vs trusted yet, but my thinking is that trusted can do anything, but private can't use trusted (it sounds like we may start selectively exposing some private interfaces to installed apps). BUG=None TEST=None Review URL: http://codereview.chromium.org/8764004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112512 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ppapi/c/DEPS')
-rw-r--r--ppapi/c/DEPS11
1 files changed, 11 insertions, 0 deletions
diff --git a/ppapi/c/DEPS b/ppapi/c/DEPS
new file mode 100644
index 0000000..aa6e7d0
--- /dev/null
+++ b/ppapi/c/DEPS
@@ -0,0 +1,11 @@
+# ppapi/c should not be dependent on other parts of chromium; it should stay
+# browser-neutral as much as possible.
+include_rules = [
+ "-base",
+ "-build",
+ "-ipc",
+ "-uncode",
+ "-testing",
+ "-ppapi",
+ "+ppapi/c",
+]