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, set the GYP_DEFINES environment | 4 Open the Chrome all.sln solution and rebuild the pepper_test_plugin and |
5 variable to "enable_pepper=1". From a Windows command prompt: | |
6 set GYP_DEFINES=enable_pepper=1 | |
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. | 5 chrome projects. |
13 | 6 |
14 To load this plugin in Chrome, use the command line flags: | 7 To load this plugin in Chrome, use the command line flags: |
15 --no-sandbox | 8 --no-sandbox |
| 9 --internal-pepper |
16 --load-plugin=<<<YOUR CHECKOUT ROOT>>\src\webkit\tools\pepper_test_plugin\Debu
g\pepper_test_plugin.dll | 10 --load-plugin=<<<YOUR CHECKOUT ROOT>>\src\webkit\tools\pepper_test_plugin\Debu
g\pepper_test_plugin.dll |
17 | 11 |
18 A simple way to launch Chrome with these command line flags is to run the | 12 A simple way to launch Chrome with these command line flags is to run the |
19 generated pepper_test_plugin project. | 13 generated pepper_test_plugin project. |
20 | 14 |
21 Note that pepper_test_plugin is not dependent on the chrome project so you | 15 Note that pepper_test_plugin is not dependent on the chrome project so you |
22 need to remember to build Chrome separately if necessary. | 16 need to remember to build Chrome separately if necessary. |
OLD | NEW |