OLD | NEW |
1 This is a test plugin for manual testing of the Pepper plugin API. See | 1 This is a test plugin for manual testing of the Pepper plugin API. See |
2 https://wiki.mozilla.org/Plugins:PlatformIndependentNPAPI | 2 https://wiki.mozilla.org/Plugins:PlatformIndependentNPAPI |
3 | 3 |
4 To generate a project from the gyp file, use: | 4 To generate a project from the gyp file, set the GYP_DEFINES environment |
5 python ..\..\..\build\gyp_chromium pepper_test_plugin.gyp | 5 variable to "enable_pepper=1". From a Windows command prompt: |
6 | 6 set GYP_DEFINES=enable_pepper=1 |
7 You need to enable PEPPER_APIS_ENABLED in src\chrome\renderer\render_view.cc in
your Chrome build. | 7 |
| 8 Then rebuild the project files: |
| 9 gclient runhooks --force |
| 10 |
| 11 Then open the Chrome all.sln solution and rebuild the pepper_test_plugin and |
| 12 chrome projects. |
8 | 13 |
9 To load this plugin in Chrome, use the command line flags: | 14 To load this plugin in Chrome, use the command line flags: |
10 --no-sandbox | 15 --no-sandbox |
11 --load-plugin=<<<YOUR CHECKOUT ROOT>>\src\webkit\tools\pepper_test_plugin\Debu
g\pepper_test_plugin.dll | 16 --load-plugin=<<<YOUR CHECKOUT ROOT>>\src\webkit\tools\pepper_test_plugin\Debu
g\pepper_test_plugin.dll |
12 | 17 |
| 18 A simple way to launch Chrome with these command line flags is to run the |
| 19 generated pepper_test_plugin project. |
| 20 |
| 21 Note that pepper_test_plugin is not dependent on the chrome project so you |
| 22 need to remember to build Chrome separately if necessary. |
OLD | NEW |