boost/more
1
0
Fork 0
mirror of https://github.com/boostorg/more.git synced 2025-03-13 11:40:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merged back from release branch.

Browse Source 
Fix up windows doc error


[SVN r50810]
This commit is contained in:
Dave Abrahams 2009-01-27 19:51:20 +00:00
parent 087b0dcd22
commit 90d0ac022f
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
getting_started/unix-variants.html
View File

@ -431,7 +431,7 @@ bjam <strong>--build-dir=</strong><a class="reference internal" href="#id10"><em
$ cd ~/<tt class="docutils literal"><span class="pre">boost_1_38_0</span></tt>
$ bjam <strong>--build-dir=</strong>/tmp/build-boost <strong>--toolset=</strong>gcc stage
</pre>
<p>That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “``--build-type=complete``”.</p>
<p>That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “<tt class="docutils literal"><span class="pre">--build-type=complete</span></tt>”.</p>
<!-- Copyright David Abrahams 2006. Distributed under the Boost -->
<!-- Software License, Version 1.0. (See accompanying -->
<!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
@ -461,7 +461,7 @@ be interested in:</p>
<p class="last">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 “``&gt;build.log 2&gt;&amp;1``” to your command line.</p>
file by appending “<tt class="docutils literal"><span class="pre">&gt;build.log</span> <span class="pre">2&gt;&amp;1</span></tt>” to your command line.</p>
</div>
</div>
</div>

2
getting_started/windows.html
View File

@ -500,7 +500,7 @@ bjam <strong>--build-dir=</strong><a class="reference internal" href="#id12"><em
C:\WINDOWS&gt; cd <tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_38_0</span></tt>
<tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_38_0</span></tt>&gt; bjam <strong>^</strong>
More? <strong>--build-dir=</strong>&quot;C:\Documents and Settings\dave\build-boost&quot; <strong>^</strong>
More? <strong>--toolset=</strong>msvc <strong>--build-type=complete</strong> stage
More? <strong>--build-type=complete</strong> <strong>msvc</strong> stage
</pre>
<p>Be sure to read <a class="reference internal" href="#continuation">this note</a> about the appearance of <tt class="docutils literal"><span class="pre">^</span></tt>,
<tt class="docutils literal"><span class="pre">More?</span></tt> and quotation marks (<tt class="docutils literal"><span class="pre">&quot;</span></tt>) in that line.</p>

2
getting_started/windows.rst
View File

@ -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=**\ msvc **--build-type=complete** stage
More? **--build-type=complete** **msvc** stage
Be sure to read `this note`__ about the appearance of ``^``,
``More?`` and quotation marks (``"``) in that line.