Subject: [Boost-commit] svn:boost r50345 - in branches/release: . more/getting_started more/getting_started/detail
From: eric_at_[hidden]
Date: 2008-12-21 12:44:34
Author: eric_niebler
Date: 2008-12-21 12:44:33 EST (Sun, 21 Dec 2008)
New Revision: 50345
URL: http://svn.boost.org/trac/boost/changeset/50345
Log:
merge GSG changes from trunk
Properties modified:
branches/release/ (props changed)
Text files modified:
branches/release/more/getting_started/detail/library-naming.rst | 3 +--
branches/release/more/getting_started/unix-variants.html | 7 +++----
branches/release/more/getting_started/windows.html | 5 ++---
3 files changed, 6 insertions(+), 9 deletions(-)
Modified: branches/release/more/getting_started/detail/library-naming.rst
==============================================================================
--- branches/release/more/getting_started/detail/library-naming.rst (original)
+++ branches/release/more/getting_started/detail/library-naming.rst 2008-12-21 12:44:33 EST (Sun, 21 Dec 2008)
@@ -67,8 +67,7 @@
convention. On most unix-style platforms the extensions are
``.a`` and ``.so`` for static libraries (archives) and shared
libraries, respectively. On Windows, ``.dll`` indicates a shared
- library and (except for static libraries built by the ``gcc``
- toolset_, whose names always end in ``.a``) ``.lib`` indicates a
+ library and ``.lib`` indicates a
static or import library. Where supported by toolsets on unix
variants, a full version extension is added (e.g. ".so.1.34") and
a symbolic link to the library file, named without the trailing
Modified: branches/release/more/getting_started/unix-variants.html
==============================================================================
--- branches/release/more/getting_started/unix-variants.html (original)
+++ branches/release/more/getting_started/unix-variants.html 2008-12-21 12:44:33 EST (Sun, 21 Dec 2008)
@@ -431,7 +431,7 @@
$ 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, “<tt class="docutils literal"><span class="pre">--build-type=complete</span></tt>â€.</p>
+<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>
<!-- 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 @@
<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 “<tt class="docutils literal"><span class="pre">>build.log</span> <span class="pre">2>&1</span></tt>†to your command line.</p>
+file by appending “``>build.log 2>&1``†to your command line.</p>
</div>
</div>
</div>
@@ -646,8 +646,7 @@
convention. On most unix-style platforms the extensions are
<tt class="docutils literal"><span class="pre">.a</span></tt> and <tt class="docutils literal"><span class="pre">.so</span></tt> for static libraries (archives) and shared
libraries, respectively. On Windows, <tt class="docutils literal"><span class="pre">.dll</span></tt> indicates a shared
-library and (except for static libraries built by the <tt class="docutils literal"><span class="pre">gcc</span></tt>
-<a class="reference internal" href="#toolset">toolset</a>, whose names always end in <tt class="docutils literal"><span class="pre">.a</span></tt>) <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a
+library and <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a
static or import library. Where supported by toolsets on unix
variants, a full version extension is added (e.g. ".so.1.34") and
a symbolic link to the library file, named without the trailing
Modified: branches/release/more/getting_started/windows.html
==============================================================================
--- branches/release/more/getting_started/windows.html (original)
+++ branches/release/more/getting_started/windows.html 2008-12-21 12:44:33 EST (Sun, 21 Dec 2008)
@@ -537,7 +537,7 @@
<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 “<tt class="docutils literal"><span class="pre">>build.log</span> <span class="pre">2>&1</span></tt>†to your command line.</p>
+file by appending “``>build.log 2>&1``†to your command line.</p>
</div>
</div>
</div>
@@ -741,8 +741,7 @@
convention. On most unix-style platforms the extensions are
<tt class="docutils literal"><span class="pre">.a</span></tt> and <tt class="docutils literal"><span class="pre">.so</span></tt> for static libraries (archives) and shared
libraries, respectively. On Windows, <tt class="docutils literal"><span class="pre">.dll</span></tt> indicates a shared
-library and (except for static libraries built by the <tt class="docutils literal"><span class="pre">gcc</span></tt>
-<a class="reference internal" href="#toolset">toolset</a>, whose names always end in <tt class="docutils literal"><span class="pre">.a</span></tt>) <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a
+library and <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a
static or import library. Where supported by toolsets on unix
variants, a full version extension is added (e.g. ".so.1.34") and
a symbolic link to the library file, named without the trailing