summaryrefslogtreecommitdiffstats
path: root/build/common.gypi
Commit message (Collapse)AuthorAgeFilesLines
* Linux: Remove -fno-asynchronous-unwind-tables. We need the eh_frame section ↵thestig@chromium.org2010-02-181-5/+0
| | | | | | | | | | to obtain backtraces on 64-bit. BUG=none TEST=Sane backtraces in 64-bit stacktraces. Review URL: http://codereview.chromium.org/626013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@39320 0039d316-1c4b-4281-b951-d872f2087c98
* media: remove redundant gyp excludesevan@chromium.org2010-02-171-2/+9
| | | | | | | | | | I moved all of these general patterns to common.gypi. Also rearrange the common.gypi patterns to cover more common Linux patterns. Review URL: http://codereview.chromium.org/608032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@39236 0039d316-1c4b-4281-b951-d872f2087c98
* Ignore .m files in addition to .mm on non-Macs.mark@chromium.org2010-02-101-1/+1
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/594031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38680 0039d316-1c4b-4281-b951-d872f2087c98
* Let the chromium_code variable be applied in target scope in addition to .gypmark@chromium.org2010-02-101-5/+18
| | | | | | | | | | | | | | | | | file scope. This extends r38519, which was incomplete. To resolve bug 33186, I am trying to turn test_shell.gyp into test_shell.gypi, and have webkit.gyp include it. webkit.gyp is not chromium_code, but the targets in test_shell.gypi are. BUG=33186 TEST=builds still work, -Werror and friends are still applied (or not) correctly Review URL: http://codereview.chromium.org/600047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38658 0039d316-1c4b-4281-b951-d872f2087c98
* Move build/external_code.gypi into build/common.gypi.mark@chromium.org2010-02-101-2/+29
| | | | | | | | BUG=35184 TEST=none Review URL: http://codereview.chromium.org/593025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38626 0039d316-1c4b-4281-b951-d872f2087c98
* Let the chromium_code variable be applied in target scope in addition to .gypmark@chromium.org2010-02-091-48/+44
| | | | | | | | | | | | | | file scope. To resolve bug 33186, I am trying to turn test_shell.gyp into test_shell.gypi, and have webkit.gyp include it. webkit.gyp is not chromium_code, but the targets in test_shell.gypi are. BUG=33186 TEST=builds still work, -Werror and friends are still applied (or not) correctly Review URL: http://codereview.chromium.org/595010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38519 0039d316-1c4b-4281-b951-d872f2087c98
* linux: build with -Wextraevan@chromium.org2010-02-051-1/+7
| | | | | | | | | | | | 95% of this is removing "const" from return types, but turning this on found one bug! (A "for" loop that expected its iterator to go negative but which was using an unsigned type.) BUG=34160 Review URL: http://codereview.chromium.org/570012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38266 0039d316-1c4b-4281-b951-d872f2087c98
* Changes necessary to compile gpu demos on linux. It is not functional yet ↵alokp@chromium.org2010-02-031-2/+5
| | | | | | | | | just compiling. BUG=26099 Review URL: http://codereview.chromium.org/552240 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37977 0039d316-1c4b-4281-b951-d872f2087c98
* [GPU] Get GPU process running on the mackbr@google.com2010-02-031-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Initial port of GPU process / plugin to Mac OS X. Uses new IOSurface APIs and therefore currently runs only on 10.6. Alternate strategy will need to be devised for 10.5. Slight UI issues remain such as GPU plugins initially showing up in the wrong place on the page. These will be fixed in follow-on bugs. Minimal changes made to command buffer code to get it to compile on Mac OS X. Commented out use of nested anonymous namespaces in gles2_cmd_decoder.cc which were causing the linker to crash with a seg fault. Refactored gyp files so the OS test enabling the GPU plugin is in one place, common.gypi, and other files test only the variable enable_gpu. Slight change to gles2_demo_cc.cc to add some simple animation to verify that updates from the GPU plugin are reaching the screen. Changed Pepper test plugin to use 3D view by default and commented out use of audio context because of recent issues. TEST=none (ran Pepper Test Plugin with 3D view enabled) BUG=http://crbug.com/25988 Review URL: http://codereview.chromium.org/558035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37934 0039d316-1c4b-4281-b951-d872f2087c98
* Use refactored filename rules in net.gyp.evan@chromium.org2010-01-291-1/+1
| | | | | | | | | | | | | build/common.gypi has some general patterns for filenames on platforms, e.g. "don't build _win.cc on non-Windows", so we don't need to duplicate them here. While I'm at it, add the FreeBSD/OpenBSD tests as well, since that was what prompted this change. Review URL: http://codereview.chromium.org/558034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37553 0039d316-1c4b-4281-b951-d872f2087c98
* linux: enable pepper pluginpiman@chromium.org2010-01-251-0/+7
| | | | | | | | | This is CL 36399 that was reverted in 36969 because it caused an ICE on the official builders. This adds a workaround for the ICE. Review URL: http://codereview.chromium.org/546136 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37055 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 36399 - linux: enable pepper_test_plugin laforge@chromium.org2010-01-231-7/+0
| | | | | | | | | | | | | | | | | This is breaking official x64 builds, notified team of break earlier in the week, but haven't seen a fix. I'm reverting now. Please fix before re-enabling. Original message: This includes a way to build it with full support on x64 (and arm ?), by specifying linux_fpic=1 in GYP_DEFINES and rerunning gyp. Review URL: http://codereview.chromium.org/551041 TBR=piman@chromium.org Review URL: http://codereview.chromium.org/548133 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36969 0039d316-1c4b-4281-b951-d872f2087c98
* GYP: recognize OpenBSD/amd64 as x64 as it's called in this worldpvalchev@google.com2010-01-231-1/+1
| | | | | | Review URL: http://codereview.chromium.org/548125 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36939 0039d316-1c4b-4281-b951-d872f2087c98
* linux: always set visibility=hiddenevan@chromium.org2010-01-211-4/+3
| | | | | | | | | | | | This is necessary to make some plugins work. Satoru has a patch to do backtraces in a different manner. BUG=32762 TEST=about:plugins doesn't call random other plugins the native client plugin Review URL: http://codereview.chromium.org/553047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36778 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r36641 "Linux: Enable TCMalloc (Take X)."kuchhal@chromium.org2010-01-211-1/+1
| | | | | | | | | | | | Apparently this change is causing random hangs on Linux buildbots. This reverts commit db71cfd0fea742eb16ec2f38d14f6a0e8aeaa7f9. TBR=willchan Review URL: http://codereview.chromium.org/555026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36724 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: Enable TCMalloc (Take X).willchan@chromium.org2010-01-201-1/+1
| | | | | | | | Async signal safe posix signal handling has landed, so this should be safe to land too. Review URL: http://codereview.chromium.org/552060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36641 0039d316-1c4b-4281-b951-d872f2087c98
* Adding a secondary mini_installer target for Chrome Frame. This will remove ↵robertshield@chromium.org2010-01-191-9/+0
| | | | | | | | | | | | | | the need to have different build scripts to build either Chrome or Chrome Frame. Also remove the now-unneeded gyp variables 'chrome_frame_define' and 'google_update_appid'. BUG=Both Chrome and Chrome Frame products should be buildable from a single solution file - we shouldn't need to run GYP with different settings to get a CF solution. TEST=none Review URL: http://codereview.chromium.org/542078 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36546 0039d316-1c4b-4281-b951-d872f2087c98
* linux: enable pepper_test_pluginpiman@chromium.org2010-01-151-0/+7
| | | | | | | | This includes a way to build it with full support on x64 (and arm ?), by specifying linux_fpic=1 in GYP_DEFINES and re-running gyp. Review URL: http://codereview.chromium.org/551041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36399 0039d316-1c4b-4281-b951-d872f2087c98
* Use no_strict_aliasing=1 by default.craig.schlenter@chromium.org2010-01-131-1/+7
| | | | | | | | | | | | | | | | | This will turn on -fno-strict-aliasing. There are regular aliasing problems in the codebase and at least one of these was not caught by -Wall -Werror so defaulting to -fno-strict-aliasing seems like a good idea especially given the increased popularity of gcc 4.4 with it's use in karmic, fedora and in chromeos chroot builds et. al. The long term plan is to have some test infrastructure in place that will test 4.4 binaries and to fix the aliasing issues. BUG=28749 Review URL: http://codereview.chromium.org/519034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36151 0039d316-1c4b-4281-b951-d872f2087c98
* linux: add host_arch detectionpiman@chromium.org2010-01-121-13/+20
| | | | | | | | BUG=31274 Review URL: http://codereview.chromium.org/547019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35993 0039d316-1c4b-4281-b951-d872f2087c98
* official build and buildbots are now chromeos=1oshima@chromium.org2010-01-091-1/+1
| | | | | | | | | | | | valgrind bots are up (they're still red tho). I believe it's ready to check this in. BUG=None TEST=None Review URL: http://codereview.chromium.org/487003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35858 0039d316-1c4b-4281-b951-d872f2087c98
* linux: implement gpu pluginpiman@chromium.org2010-01-061-4/+1
| | | | | | | | Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=35509 Review URL: http://codereview.chromium.org/500132 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35612 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 35509 - linux: implement gpu pluginpiman@chromium.org2010-01-051-1/+4
| | | | | | | | | Review URL: http://codereview.chromium.org/500132 TBR=piman@chromium.org Review URL: http://codereview.chromium.org/525022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35511 0039d316-1c4b-4281-b951-d872f2087c98
* linux: implement gpu pluginpiman@chromium.org2010-01-051-4/+1
| | | | | | Review URL: http://codereview.chromium.org/500132 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35509 0039d316-1c4b-4281-b951-d872f2087c98
* Removing the last remaining vsprops files (that are hooked in).bradnelson@google.com2010-01-041-9/+18
| | | | | | | | | | | | | Also pulling in a newer nacl version. Switching to use AdditionalOptions in list form. BUG=None TEST=None TBR=mmentovai Review URL: http://codereview.chromium.org/523027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35449 0039d316-1c4b-4281-b951-d872f2087c98
* linux: reenable symbols in backtraces in debug buildsevan@chromium.org2009-12-311-1/+4
| | | | | | | | This is easy enough to fix, and would be occasionally helpful. Review URL: http://codereview.chromium.org/524015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35405 0039d316-1c4b-4281-b951-d872f2087c98
* Apply -lgcov link to type loadable_bundle when building coverage=1.jrg@chromium.org2009-12-281-3/+4
| | | | | | Review URL: http://codereview.chromium.org/515045 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35307 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 35189 (caused test_shell_tests crashes on valgrind bot):willchan@chromium.org2009-12-231-1/+1
| | | | | | | | | | | | | | Take 2: Reenable TCMalloc on Linux and make POSIX signal handling async signal safe. Reinstates r34096 and r34036, which were reverted by r34632 due to hanging ui_tests and browser_tests on bots. I've been unable to repro on the trybots despite hitting them with a ton of try jobs, so I'm trying on the buildbots again. BUG=http://crbug.com/30501 Review URL: http://codereview.chromium.org/505068 TBR=willchan@chromium.org Review URL: http://codereview.chromium.org/517001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35192 0039d316-1c4b-4281-b951-d872f2087c98
* Take 2: Re-enable TCMalloc on Linux and make POSIX signal handling async ↵willchan@chromium.org2009-12-221-1/+1
| | | | | | | | | | | | signal safe. Reinstates r34096 and r34036, which were reverted by r34632 due to hanging ui_tests and browser_tests on bots. I've been unable to repro on the trybots despite hitting them with a ton of try jobs, so I'm trying on the buildbots again. BUG=http://crbug.com/30501 Review URL: http://codereview.chromium.org/505068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35189 0039d316-1c4b-4281-b951-d872f2087c98
* Change chromeos build to use viewsoshima@chromium.org2009-12-221-6/+3
| | | | | | | | | BUG=None TEST=None Review URL: http://codereview.chromium.org/508025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35186 0039d316-1c4b-4281-b951-d872f2087c98
* Added Pepper 3D device that instantiates the GPU plugin and sends GLES2 ↵apatrick@google.com2009-12-221-6/+8
| | | | | | | | | | | | | | | | | | | | | | | commands to it via a command buffer. Added API for managing buffers to Pepper 3D device. Removed DCHECK from WebPluginImpl::SetWindow that checks against a windowless plugin being given a window handle. Please check this! Now an initially windowless plugin instance gets a handle when it requests a Pepper 3D context. Perhaps the window handle should be concealed from the underlying plugin isntance. Removed enable_gpu gyp variable and C macro. GPU code is always built on windows but not mac or linux. It is enabled at runtime with the --enable-gpu-plugin switch. Redesigned CommandBuffer interface so it exposes shared memory through a Buffer. This was necessary because Pepper has no notion of shared memory handles. The Buffer exposes the shared memory as both a handle (through base::SharedMemory) and the mapped address and size. Refactored CommandBufferEngine so mapped shared memory addresses and sizes are returned with a single call rather than two separate calls. Added 3D demo to pepper test plugin. TEST=try servers BUG=none Review URL: http://codereview.chromium.org/367002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35185 0039d316-1c4b-4281-b951-d872f2087c98
* Refactoring build configurations - make it clearer and allow better support ↵gregoryd@google.com2009-12-221-46/+86
| | | | | | | | | | | | | for x64 on Windows TEST=none BUG=29467 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=35012 Review URL: http://codereview.chromium.org/501127 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35129 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 35012 - Rearrange build configurations make it clearer and allow ↵gregoryd@google.com2009-12-191-85/+45
| | | | | | | | | | | | | | better support for x64 on Windows TEST=none BUG=29467 Review URL: http://codereview.chromium.org/501127 TBR=gregoryd@google.com Review URL: http://codereview.chromium.org/500149 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35016 0039d316-1c4b-4281-b951-d872f2087c98
* Rearrange build configurations - make it clearer and allow better support ↵gregoryd@google.com2009-12-191-45/+85
| | | | | | | | | | | for x64 on Windows TEST=none BUG=29467 Review URL: http://codereview.chromium.org/501127 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35012 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 34983 - Split more targets from chrome.gyp to add support for ↵slightlyoff@chromium.org2009-12-181-14/+0
| | | | | | | | | | | | | | | | | building Native Client for 64bit Windows. This CL is required for supporting Native Client on 64bit Windows. On Win64 we will use a 64bit executable to load NaCl modules. Since we have only one version of Chrome on Windows, this executable has to be built together with 32bit Chrome binaries. For the targets that are required for both 32bit and 64bit builds, this CL moves the shared parts of the target definitions into targetspecific gypi files (such as base.gypi). New 64bit only targets are added. Since we would like to port as few code as possible at this point, some 64bit targets include less source files or less dependencies than the original 32bit targets. These targets will have nacl_win64 in their name to emphasize that they should be used for NaCl only. Some 64bit targets are identical to the 32bit targets in everything except for the target platform these will have only win64 in their name. TEST=none BUG=28176 Review URL: http://codereview.chromium.org/384068 TBR=gregoryd@google.com Review URL: http://codereview.chromium.org/501125 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34990 0039d316-1c4b-4281-b951-d872f2087c98
* Split more targets from chrome.gyp to add support for building Native Client ↵gregoryd@google.com2009-12-181-0/+14
| | | | | | | | | | | | | for 64-bit Windows. This CL is required for supporting Native Client on 64-bit Windows. On Win64 we will use a 64-bit executable to load NaCl modules. Since we have only one version of Chrome on Windows, this executable has to be built together with 32-bit Chrome binaries. For the targets that are required for both 32-bit and 64-bit builds, this CL moves the shared parts of the target definitions into target-specific gypi files (such as base.gypi). New 64-bit only targets are added. Since we would like to port as few code as possible at this point, some 64-bit targets include less source files or less dependencies than the original 32-bit targets. These targets will have nacl_win64 in their name - to emphasize that they should be used for NaCl only. Some 64-bit targets are identical to the 32-bit targets in everything except for the target platform - these will have only win64 in their name. TEST=none BUG=28176 Review URL: http://codereview.chromium.org/384068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34983 0039d316-1c4b-4281-b951-d872f2087c98
* OpenBSD defines.benl@chromium.org2009-12-171-7/+11
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34829 0039d316-1c4b-4281-b951-d872f2087c98
* Fix Linux hanging ui_tests and browser_tests by reverting posix signal ↵willchan@chromium.org2009-12-161-1/+1
| | | | | | | | | | | | | handler changes. Reverts: r34036 - "Make POSIX SIGTERM/SIGINT/SIGHUP handler async signal safe." r34096 - "Re-enable TCMalloc on Linux." This change depended on the posix signal handler change. BUG=http://crbug.com/30501 Review URL: http://codereview.chromium.org/502017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34632 0039d316-1c4b-4281-b951-d872f2087c98
* Yet again, trying to land switch to win7 sdk.bradnelson@google.com2009-12-121-3/+3
| | | | | | | | | BUG=None TEST=None Review URL: http://codereview.chromium.org/490026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34433 0039d316-1c4b-4281-b951-d872f2087c98
* Changes to build/ from a combination of FreeBSD and OpenBSD patches.evan@chromium.org2009-12-111-7/+16
| | | | | | Review URL: http://codereview.chromium.org/491053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34371 0039d316-1c4b-4281-b951-d872f2087c98
* Reverting sdk7 landing AGAIN!!!bradnelson@google.com2009-12-111-3/+3
| | | | | | | | | | | | | Something is still fishy on the bots. BUG=None TEST=None TBR=maruel Review URL: http://codereview.chromium.org/491050 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34358 0039d316-1c4b-4281-b951-d872f2087c98
* Reconstructing 34247 / 479007bradnelson@google.com2009-12-111-3/+3
| | | | | | | | | | | | | Giving it another go on the bots. I think I know what went wrong. BUG=None TEST=None TBR=maruel Review URL: http://codereview.chromium.org/491021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34355 0039d316-1c4b-4281-b951-d872f2087c98
* Reverting 34267.bradnelson@google.com2009-12-101-3/+3
| | | | | | | | | | | | Too much red. BUG=None TEST=None TBR=maruel Review URL: http://codereview.chromium.org/486018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34269 0039d316-1c4b-4281-b951-d872f2087c98
* Switching platform sdk hermetic fallback to 7.0bradnelson@google.com2009-12-101-3/+3
| | | | | | | | | | BUG=None TEST=None Review URL: http://codereview.chromium.org/479007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34267 0039d316-1c4b-4281-b951-d872f2087c98
* Make sure the 'use_system_*' variables are actually visible in the relevant ↵mmoss@google.com2009-12-101-14/+0
| | | | | | | | | | | | | | gyp files. Retrying r34195, this time without libxslt, since we don't want to use the system version of that if we're not also using system libxml (merged from http://codereview.chromium.org/481011). BUG=29738 Review URL: http://codereview.chromium.org/486012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34255 0039d316-1c4b-4281-b951-d872f2087c98
* Re-enable the build of Pepper support by default (issue 464074, svn revision ↵sehr@google.com2009-12-101-4/+4
| | | | | | | | | | | | | | | | | 34161). There were problems building Skia and others for the 64-bit linux versions of the Pepper test plugin, so I have disabled building that plugin except on Windows for now and added a TODO. One significant addition to the previous comment lines. The flag enable_gpu=1 now causes the build definition ENABLE_GPU=1 to allow guarding of dependent code. BUG=none TEST=none Review URL: http://codereview.chromium.org/481001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34227 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 34195 - Make sure the 'use_system_*' variables are actually visible ↵jrg@chromium.org2009-12-101-0/+14
| | | | | | | | | | | | | | | | | | | | | in the relevant gyp files. BUG=29738 Review URL: http://codereview.chromium.org/479005 TBR=mmoss@google.com Example choke: http://build.chromium.org/buildbot/waterfall/builders/Linux%20Perf/builds/4382/steps/compile/logs/stdio Compiling /b/slave/chromium-rel-linux-hardy/build/src/sconsbuild/Release/obj/chrome/unit_tests/common/bzip2_unittest.o /b/slave/chromium-rel-linux-hardy/build/src/chrome/common/bzip2_unittest.cc:6:19: error: bzlib.h: No such file or directory Review URL: http://codereview.chromium.org/484003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34213 0039d316-1c4b-4281-b951-d872f2087c98
* Make sure the 'use_system_*' variables are actually visible in the relevant ↵mmoss@google.com2009-12-091-14/+0
| | | | | | | | | | gyp files. BUG=29738 Review URL: http://codereview.chromium.org/479005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34195 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 34161 - Enable Pepper support by default, including building the test ↵sehr@google.com2009-12-091-2/+5
| | | | | | | | | | | | | | | | | | | | 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 internalpepper 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 TBR=sehr@google.com Review URL: http://codereview.chromium.org/475004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34162 0039d316-1c4b-4281-b951-d872f2087c98
* Enable Pepper support by default, including building the test plugin.sehr@google.com2009-12-091-5/+2
| | | | | | | | | | | | | | | 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