From b11afaf2c35bca16adae6595bda8999b8d0bcf60 Mon Sep 17 00:00:00 2001 From: "dmichael@chromium.org" Date: Thu, 17 May 2012 22:25:10 +0000 Subject: PPAPI/NaCl: Make a gyp flag for including the untrusted IPC proxy. This way, those of us working on the proxy switch need only add: { 'variables': { 'build_ppapi_ipc_proxy_untrusted': '1', }, } to "~/.gyp/include.gypi" ...and we'll be able to build our untrusted targets without editing all.gyp. For anybody who doesn't set that flag, our ppapi_proxy_untrusted.gypi file will still be parsed, but it doesn't matter if the source files build (or even exist). BUG=116317 TEST= Review URL: https://chromiumcodereview.appspot.com/10399068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@137751 0039d316-1c4b-4281-b951-d872f2087c98 --- ppapi/ppapi.gyp | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'ppapi/ppapi.gyp') diff --git a/ppapi/ppapi.gyp b/ppapi/ppapi.gyp index 2c3323a..7d490f7 100644 --- a/ppapi/ppapi.gyp +++ b/ppapi/ppapi.gyp @@ -7,6 +7,11 @@ # in the .gyp files (since ppapi_internal depends on parts of Chrome). { + 'conditions': [ + ['disable_nacl==0 and build_ppapi_ipc_proxy_untrusted==1', { + 'includes': ['ppapi_proxy_untrusted.gypi'], + }], + ], 'variables': { 'chromium_code': 1, # Use higher warning level. }, -- cgit v1.1