| OLD | NEW |
| 1 # PDFium | 1 # PDFium |
| 2 | 2 |
| 3 ## Prerequisites | 3 ## Prerequisites |
| 4 | 4 |
| 5 Get the chromium depot tools via the instructions at | 5 Get the chromium depot tools via the instructions at |
| 6 http://www.chromium.org/developers/how-tos/install-depot-tools (this provides | 6 http://www.chromium.org/developers/how-tos/install-depot-tools (this provides |
| 7 the gclient utilty needed below). | 7 the gclient utilty needed below). |
| 8 | 8 |
| 9 Also install Python, Subversion, and Git and make sure they're in your path. | 9 Also install Python, Subversion, and Git and make sure they're in your path. |
| 10 | 10 |
| (...skipping 10 matching lines...) Expand all Loading... |
| 21 | 21 |
| 22 We use the GYP library to generate the build files. | 22 We use the GYP library to generate the build files. |
| 23 | 23 |
| 24 At this point, you have two options. The first option is to use the [Ninja] | 24 At this point, you have two options. The first option is to use the [Ninja] |
| 25 (http://martine.github.io/ninja/) build system (also included with the | 25 (http://martine.github.io/ninja/) build system (also included with the |
| 26 depot\_tools checkout). This is the default as of mid-September, 2015. | 26 depot\_tools checkout). This is the default as of mid-September, 2015. |
| 27 Previously, the second option (platform-specific build files) was the default. | 27 Previously, the second option (platform-specific build files) was the default. |
| 28 Most PDFium developers use Ninja, as does our [continuous build system] | 28 Most PDFium developers use Ninja, as does our [continuous build system] |
| 29 (http://build.chromium.org/p/client.pdfium/). | 29 (http://build.chromium.org/p/client.pdfium/). |
| 30 | 30 |
| 31 * On Windows: `build\gyp\_pdfium` | 31 * On Windows: `build\gyp_pdfium` |
| 32 * For all other platforms: `build/gyp\_pdfium` | 32 * For all other platforms: `build/gyp_pdfium` |
| 33 | 33 |
| 34 The second option is to generate platform-specific build files, i.e. Makefiles | 34 The second option is to generate platform-specific build files, i.e. Makefiles |
| 35 on Linux, sln files on Windows, and xcodeproj files on Mac. To do so, set the | 35 on Linux, sln files on Windows, and xcodeproj files on Mac. To do so, set the |
| 36 GYP\_GENERATORS environment variable appropriately (e.g. "make", "msvs", or | 36 GYP\_GENERATORS environment variable appropriately (e.g. "make", "msvs", or |
| 37 "xcode") before running the above command. | 37 "xcode") before running the above command. |
| 38 | 38 |
| 39 ## Building the code | 39 ## Building the code |
| 40 | 40 |
| 41 If you used Ninja, you can build the sample program by: `ninja -C out/Debug | 41 If you used Ninja, you can build the sample program by: `ninja -C out/Debug |
| 42 pdfium\_test` You can build the entire product (which includes a few unit | 42 pdfium_test` You can build the entire product (which includes a few unit |
| 43 tests) by: `ninja -C out/Debug`. | 43 tests) by: `ninja -C out/Debug`. |
| 44 | 44 |
| 45 If you're not using Ninja, then building is platform-specific. | 45 If you're not using Ninja, then building is platform-specific. |
| 46 | 46 |
| 47 * On Linux: `make pdfium\_test` | 47 * On Linux: `make pdfium_test` |
| 48 * On Mac: `open build/all.xcodeproj` | 48 * On Mac: `open build/all.xcodeproj` |
| 49 * On Windows: open build\all.sln | 49 * On Windows: open build\all.sln |
| 50 | 50 |
| 51 ## Running the sample program | 51 ## Running the sample program |
| 52 | 52 |
| 53 The pdfium\_test program supports reading, parsing, and rasterizing the pages of | 53 The pdfium\_test program supports reading, parsing, and rasterizing the pages of |
| 54 a .pdf file to .ppm or .png output image files (windows supports two other | 54 a .pdf file to .ppm or .png output image files (windows supports two other |
| 55 formats). For example: `out/Debug/pdfium\_test --ppm path/to/myfile.pdf`. Note | 55 formats). For example: `out/Debug/pdfium_test --ppm path/to/myfile.pdf`. Note |
| 56 that this will write output images to `path/to/myfile.pdf.<n>.ppm`. | 56 that this will write output images to `path/to/myfile.pdf.<n>.ppm`. |
| 57 | 57 |
| 58 ## Testing | 58 ## Testing |
| 59 | 59 |
| 60 There are currently several test suites that can be run: | 60 There are currently several test suites that can be run: |
| 61 | 61 |
| 62 * pdfium\_unittests | 62 * pdfium\_unittests |
| 63 * pdfium\_embeddertests | 63 * pdfium\_embeddertests |
| 64 * testing/tools/run\_corpus\_tests.py | 64 * testing/tools/run\_corpus\_tests.py |
| 65 * testing/tools/run\_javascript\_tests.py | 65 * testing/tools/run\_javascript\_tests.py |
| (...skipping 54 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 120 ``` | 120 ``` |
| 121 git checkout origin/xfa | 121 git checkout origin/xfa |
| 122 git checkout -b merge_branch | 122 git checkout -b merge_branch |
| 123 git branch --set-upstream-to=origin/xfa | 123 git branch --set-upstream-to=origin/xfa |
| 124 git cherry-pick -x <commit hash> | 124 git cherry-pick -x <commit hash> |
| 125 git commit --amend # add Merge to XFA | 125 git commit --amend # add Merge to XFA |
| 126 git cl upload | 126 git cl upload |
| 127 ``` | 127 ``` |
| 128 | 128 |
| 129 Then wait for approval, and `git cl land` | 129 Then wait for approval, and `git cl land` |
| OLD | NEW |