| OLD | NEW |
|---|
| 1 Windows | 1 Windows |
| 2 ======= | 2 ======= |
| 3 | 3 |
| 4 Prerequisites | 4 Prerequisites |
| 5 ------------- | 5 ------------- |
| 6 | 6 |
| 7 Make sure the following have been installed: | 7 Make sure the following have been installed: |
| 8 | 8 |
| 9 * Visual C++ 2013 Express or later, available for free | 9 * Visual C++ 2013 Express or later, available for free |
| 10 * http://www.visualstudio.com/downloads/download-visual-studio-vs#d-express-
windows-8 | 10 * http://www.visualstudio.com/downloads/download-visual-studio-vs#d-express-
windows-8 |
| (...skipping 27 matching lines...) Expand all Loading... |
| 38 | 38 |
| 39 Generate Visual Studio projects | 39 Generate Visual Studio projects |
| 40 ------------------------------- | 40 ------------------------------- |
| 41 | 41 |
| 42 We use the open-source gyp tool to generate Visual Studio projects (and | 42 We use the open-source gyp tool to generate Visual Studio projects (and |
| 43 analogous build scripts on other platforms) from our multi-platform "gyp" | 43 analogous build scripts on other platforms) from our multi-platform "gyp" |
| 44 files. | 44 files. |
| 45 | 45 |
| 46 You can generate the Visual Studio projects by running gyp_skia, as follows: | 46 You can generate the Visual Studio projects by running gyp_skia, as follows: |
| 47 | 47 |
| 48 (setup GYP_GENERATORS, see just below) |
| 48 cd %SKIA_CHECKOUT_DIR% | 49 cd %SKIA_CHECKOUT_DIR% |
| 49 python gyp_skia | 50 python gyp_skia |
| 50 | 51 |
| 51 This will produce Visual Studio projects in the `%SKIA_CHECKOUT_DIR%\out` direct
ory. | 52 If you like to develop from a fully-integrated Visual Studio, set |
| 53 GYP_GENERATORS=ninja,msvs-ninja before running gyp_skia to generate |
| 54 Visual-Studio-compatible project files that still ultimately build using ninja, |
| 55 or set it to msvs to use Visual Studio's own (slower) build system. If you are |
| 56 comfortable with and prefer running ninja yourself, GYP_GENERATORS=ninja is |
| 57 considerably faster than the other two options. |
| 52 | 58 |
| 53 Build and run tests from the command line | 59 Build and run tests from the command line |
| 54 ----------------------------------------- | 60 ----------------------------------------- |
| 55 | 61 |
| 56 ninja -C out\Debug dm | 62 ninja -C out\Debug dm |
| 57 out\Debug\dm | 63 out\Debug\dm |
| 58 | 64 |
| 59 Normally you should run tests in Debug mode (SK_DEBUG is defined, and debug | 65 Normally you should run tests in Debug mode (SK_DEBUG is defined, and debug |
| 60 symbols are included in the binary). If you would like to build the Release | 66 symbols are included in the binary). If you would like to build the Release |
| 61 version instead: | 67 version instead: |
| (...skipping 25 matching lines...) Expand all Loading... |
| 87 * left-arrow key: cycle through rendering methods for each test page | 93 * left-arrow key: cycle through rendering methods for each test page |
| 88 * other keys are defined in SampleApp.cpp’s SampleWindow::onHandleKey() and
SampleWindow::onHandleChar() methods | 94 * other keys are defined in SampleApp.cpp’s SampleWindow::onHandleKey() and
SampleWindow::onHandleChar() methods |
| 89 | 95 |
| 90 Build and run nanobench (performance testbench) from the command line | 96 Build and run nanobench (performance testbench) from the command line |
| 91 --------------------------------------------------------------------- | 97 --------------------------------------------------------------------- |
| 92 | 98 |
| 93 Since nanobench tests performance, it usually makes more sense to run it in Rele
ase mode. | 99 Since nanobench tests performance, it usually makes more sense to run it in Rele
ase mode. |
| 94 | 100 |
| 95 ninja -C out\Release nanobench | 101 ninja -C out\Release nanobench |
| 96 out\Release\nanobench | 102 out\Release\nanobench |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 1275753002:
Rephrase Windows gyp instructions (Closed)
Base URL: https://skia.googlesource.com/skia.git@master