|
|
@@ -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 “``>build.log 2>&1``” to your command line.</p>
|
|
|
+file by appending “<tt class="docutils literal"><span class="pre">>build.log</span> <span class="pre">2>&1</span></tt>” to your command line.</p>
|
|
|
</div>
|
|
|
</div>
|
|
|
</div>
|