[Boost-commit] svn:boost r49525 - in trunk/more/getting_started: . detail

Subject: [Boost-commit] svn:boost r49525 - in trunk/more/getting_started: . detail
From: dave_at_[hidden]
Date: 2008-11-01 15:34:36

Author: dave
Date: 2008-11-01 15:34:35 EDT (Sat, 01 Nov 2008)
New Revision: 49525
URL: http://svn.boost.org/trac/boost/changeset/49525

Log:
Added information about redirecting build output into a file.

Text files modified: 
   trunk/more/getting_started/detail/build-from-source-tail.rst |     5 +++++                                   
   trunk/more/getting_started/unix-variants.html                |     7 +++++++                                 
   trunk/more/getting_started/windows.html                      |    27 ++++++++++++++++++---------             
   3 files changed, 30 insertions(+), 9 deletions(-)

Modified: trunk/more/getting_started/detail/build-from-source-tail.rst
==============================================================================
--- trunk/more/getting_started/detail/build-from-source-tail.rst	(original)
+++ trunk/more/getting_started/detail/build-from-source-tail.rst	2008-11-01 15:34:35 EDT (Sat, 01 Nov 2008)
@@ -23,6 +23,11 @@
 * choosing a specific build variant by adding ``release`` or
   ``debug`` to the command line.
 
+.. Note:: 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.
+
 Expected Build Output
 ---------------------
 

Modified: trunk/more/getting_started/unix-variants.html
==============================================================================
--- trunk/more/getting_started/unix-variants.html	(original)
+++ trunk/more/getting_started/unix-variants.html	2008-11-01 15:34:35 EDT (Sat, 01 Nov 2008)
@@ -456,6 +456,13 @@
 <li>choosing a specific build variant by adding <tt class="docutils literal"><span class="pre">release</span></tt> or
 <tt class="docutils literal"><span class="pre">debug</span></tt> to the command line.</li>
 </ul>
+<div class="note">
+<p class="first admonition-title">Note</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>
+</div>
 </div>
 </div>
 <div class="section" id="expected-build-output">

Modified: trunk/more/getting_started/windows.html
==============================================================================
--- trunk/more/getting_started/windows.html	(original)
+++ trunk/more/getting_started/windows.html	2008-11-01 15:34:35 EDT (Sat, 01 Nov 2008)
@@ -60,14 +60,16 @@
 </div>
 <div class="section" id="get-boost">
 <h1><a class="toc-backref" href="#id26">1&nbsp;&nbsp;&nbsp;Get Boost</a></h1>
-<p>The easiest way to get a copy of Boost is to use an installer.
-The <a class="reference external" href="http://www.boost.org/doc/libs/1_36_0/more/getting_started/index.html">Boost website version of this Getting Started guide</a> will
-have undated information on installers as they become available,
-or see <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&amp;package_id=8041">Boost downloads</a> or the <a class="reference external" href="http://www.boostpro.com/products/free">installer</a> provided by <a class="reference external" href="http://www.boostpro.com">BoostPro Computing</a>.  We especially recommend using
-an installer if you use Microsoft Visual Studio, because the installer can download and install
-precompiled library binaries, saving you the trouble of building
-them yourself.  To complete this tutorial, you'll need to at least
-install the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a> binaries when given the option.</p>
+<p>The easiest way to get a copy of Boost is to use an installer.  The
+<a class="reference external" href="http://www.boost.org/doc/libs/1_36_0/more/getting_started/index.html">Boost website version of this Getting Started guide</a> will have
+undated information on installers as they become available, or see
+<a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&amp;package_id=8041">Boost downloads</a> or the <a class="reference external" href="http://www.boostpro.com/products/free">installer</a> provided by <a class="reference external" href="http://www.boostpro.com">BoostPro
+Computing</a>.  We especially recommend using an installer if you use
+Microsoft Visual Studio, because the installer can download and
+install precompiled library binaries, saving you the trouble of
+building them yourself.  To complete this tutorial, you'll need to at
+least install the Static Multithreaded variants of the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a>
+binaries when given the option.</p>
 <p>If you're using an earlier version of Visual Studio or some other
 compiler, or if you prefer to build everything yourself, you can
 download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&amp;package_id=8041"><tt class="docutils literal"><span class="pre">boost_1_37_0</span></tt><tt class="docutils literal"><span class="pre">.7z</span></tt></a> or <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&amp;package_id=8041"><tt class="docutils literal"><span class="pre">boost_1_37_0</span></tt><tt class="docutils literal"><span class="pre">.zip</span></tt></a> and unpack it to install a complete Boost
@@ -341,7 +343,7 @@
 you'll need to acquire library binaries.</p>
 <div class="section" id="install-visual-studio-binaries">
 <h2><a class="toc-backref" href="#id34">5.1&nbsp;&nbsp;&nbsp;Install Visual Studio Binaries</a></h2>
-<p>The installers will download and
+<p>The installers supplied by BoostPro Computing will download and
 install pre-compiled binaries into the <tt class="docutils literal"><span class="pre">lib\</span></tt> subdirectory of the
 boost root, typically <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_37_0</span></tt><tt class="docutils literal"><span class="pre">\lib\</span></tt>.  If you installed
 all variants of the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a> binary, you're done with this
@@ -530,6 +532,13 @@
 <li>choosing a specific build variant by adding <tt class="docutils literal"><span class="pre">release</span></tt> or
 <tt class="docutils literal"><span class="pre">debug</span></tt> to the command line.</li>
 </ul>
+<div class="note">
+<p class="first admonition-title">Note</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>
+</div>
 </div>
 </div>
 <div class="section" id="expected-build-output">