summaryrefslogtreecommitdiffstats
path: root/chrome/chrome_renderer.gypi
diff options
context:
space:
mode:
authorsehr@google.com <sehr@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2009-12-09 17:19:22 +0000
committersehr@google.com <sehr@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2009-12-09 17:19:22 +0000
commit5f6397ecb4c7bc92295adc8d21bd87e698ac5622 (patch)
tree140bdcb6f5680147521296fabd1dafcb9159a892 /chrome/chrome_renderer.gypi
parente5307cef6dcdc2ab5d4445cd57938dbf4d5e30c3 (diff)
downloadchromium_src-5f6397ecb4c7bc92295adc8d21bd87e698ac5622.zip
chromium_src-5f6397ecb4c7bc92295adc8d21bd87e698ac5622.tar.gz
chromium_src-5f6397ecb4c7bc92295adc8d21bd87e698ac5622.tar.bz2
Enable Pepper support by default, including building the test plugin.
This is needed because the NaCl plugin code that runs in the renderer needs to use Pepper APIs all the time, and NaCl support has been enabled by default for several months now. To cause an untrusted Pepper plugin to run in the renderer one needs to specify the --internal-pepper flag. I have also removed the enable_pepper flag from gyp. As the build of the GPU process was tied to this flag, I have renamed the flag to enable_gpu. TEST=none BUG=none Review URL: http://codereview.chromium.org/464074 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34161 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_renderer.gypi')
-rwxr-xr-xchrome/chrome_renderer.gypi2
1 files changed, 1 insertions, 1 deletions
diff --git a/chrome/chrome_renderer.gypi b/chrome/chrome_renderer.gypi
index f1e7c36c..ebe31de 100755
--- a/chrome/chrome_renderer.gypi
+++ b/chrome/chrome_renderer.gypi
@@ -148,7 +148,7 @@
],
},
'conditions': [
- ['enable_pepper==1', {
+ ['enable_gpu==1', {
'dependencies': [
'../gpu/gpu.gyp:gpu_plugin',
],