diff --git a/getting_started/windows.html b/getting_started/windows.html
index 41a2a7b..ed29ec8 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -500,7 +500,7 @@ bjam --build-dir=C:\Program Files\boost\boost_1_38_0
C:\Program Files\boost\boost_1_38_0> bjam ^
More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
-More? --toolset= --build-type=complete msvc stage
+More? --toolset=msvc --build-type=complete stage
Be sure to read this note about the appearance of ^,
More? and quotation marks (") in that line.
Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure everything is went well, you might redirect the output into a -file by appending “``>build.log 2>&1``” to your command line.
+file by appending “>build.log 2>&1” to your command line. diff --git a/getting_started/windows.rst b/getting_started/windows.rst index 6026dd7..40daf42 100644 --- a/getting_started/windows.rst +++ b/getting_started/windows.rst @@ -215,7 +215,7 @@ For example, your session might look like this: [#continuation]_ C:\\WINDOWS> cd |default-root| |default-root|> bjam **^** More? **--build-dir=**\ "C:\\Documents and Settings\\dave\\build-boost" **^** - More? **--toolset=**\ **--build-type=complete** msvc stage + More? **--toolset=**\ msvc **--build-type=complete** stage Be sure to read `this note`__ about the appearance of ``^``, ``More?`` and quotation marks (``"``) in that line.