aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar mtklein <mtklein@chromium.org>2015-08-05 16:18:03 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2015-08-05 16:18:03 -0700
commit1a3976795b2e3758ccec121771b890b6b10a648e (patch)
treec284a7350a5a81be277b265ba7fd826040c57daa /site
parent4fc6ff22c87a2eb89a3b9a8467a8d0e1f24e1833 (diff)
Rephrase Windows gyp instructions
The existing instructions seem misleading. BUG=skia: NOTRY=true DOCS_PREVIEW= https://skia.org/?cl=1275753002 Review URL: https://codereview.chromium.org/1275753002
Diffstat (limited to 'site')
-rw-r--r--site/user/quick/windows.md8
1 files changed, 7 insertions, 1 deletions
diff --git a/site/user/quick/windows.md b/site/user/quick/windows.md
index 53eb5d9a2e..fa00376064 100644
--- a/site/user/quick/windows.md
+++ b/site/user/quick/windows.md
@@ -45,10 +45,16 @@ files.
You can generate the Visual Studio projects by running gyp_skia, as follows:
+ (setup GYP_GENERATORS, see just below)
cd %SKIA_CHECKOUT_DIR%
python gyp_skia
-This will produce Visual Studio projects in the `%SKIA_CHECKOUT_DIR%\out` directory.
+If you like to develop from a fully-integrated Visual Studio, set
+GYP_GENERATORS=ninja,msvs-ninja before running gyp_skia to generate
+Visual-Studio-compatible project files that still ultimately build using ninja,
+or set it to msvs to use Visual Studio's own (slower) build system. If you are
+comfortable with and prefer running ninja yourself, GYP_GENERATORS=ninja is
+considerably faster than the other two options.
Build and run tests from the command line
-----------------------------------------