Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r49562 - trunk/more/getting_started
From: bdawes_at_[hidden]
Date: 2008-11-03 10:38:36

Next message: asutton_at_[hidden]: "[Boost-commit] svn:boost r49563 - in trunk: boost/graph libs/graph/test"
Previous message: asutton_at_[hidden]: "[Boost-commit] svn:boost r49561 - in trunk: boost/graph libs/graph/doc libs/graph/test"

Author: bemandawes
Date: 2008-11-03 10:38:36 EST (Mon, 03 Nov 2008)
New Revision: 49562
URL: http://svn.boost.org/trac/boost/changeset/49562

Log:
Prep for 1.38.0
Text files modified:
   trunk/more/getting_started/unix-variants.html | 22 +++++++++++-----------
   trunk/more/getting_started/windows.html | 30 +++++++++++++++---------------
   2 files changed, 26 insertions(+), 26 deletions(-)

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-03 10:38:36 EST (Mon, 03 Nov 2008)
@@ -63,12 +63,12 @@
The most reliable way to get a copy of Boost is to download a
distribution from <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041">SourceForge</a>:
<ol class="arabic">
-<li>Download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal">boost_1_37_0</tt><tt class="docutils literal">.tar.bz2</tt></a>.
+<li>Download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal">boost_1_38_0</tt><tt class="docutils literal">.tar.bz2</tt></a>.
</li>
<li>In the directory where you want to put the Boost installation,
execute
<pre class="literal-block">
-tar --bzip2 -xf /path/to/<tt class="docutils literal">boost_1_37_0</tt>.tar.bz2
+tar --bzip2 -xf /path/to/<tt class="docutils literal">boost_1_38_0</tt>.tar.bz2
</pre>
</li>
</ol>
@@ -91,7 +91,7 @@
<h1><a class="toc-backref" href="#id19">2   The Boost Distribution</a></h1>
This is a sketch of the resulting directory structure:
<pre class="literal-block">
-boost_1_37_0/ .................The â€œboost root directoryâ€
+boost_1_38_0/ .................The â€œboost root directoryâ€
 index.htm .........A copy of www.boost.org starts here
 boost/ .........................All Boost Header files
 <tt class="docutils literal"> </tt>
@@ -136,7 +136,7 @@
</div>
It's important to note the following:
<ol class="arabic" id="boost-root-directory">
-<li>The path to the boost root directory (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_37_0</tt>) is
+<li>The path to the boost root directory (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_38_0</tt>) is
sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and
mailing lists .
</li>
@@ -230,7 +230,7 @@
Now, in the directory where you saved <tt class="docutils literal">example.cpp</tt>, issue the
following command:
<pre class="literal-block">
-c++ -I path/to/<tt class="docutils literal">boost_1_37_0</tt> example.cpp -o example
+c++ -I path/to/<tt class="docutils literal">boost_1_38_0</tt> example.cpp -o example
</pre>
To test the result, type:
<pre class="literal-block">
@@ -261,7 +261,7 @@
Issue the following commands in the shell (don't type <tt class="docutils literal">$</tt>; that
represents the shell's prompt):
<pre class="literal-block">
-$ cd path/to/<tt class="docutils literal">boost_1_37_0</tt>
+$ cd path/to/<tt class="docutils literal">boost_1_38_0</tt>
$ ./configure --help
</pre>
Select your configuration options and invoke <tt class="docutils literal">./configure</tt> again
@@ -428,10 +428,10 @@
</pre>
For example, your session might look like this:
<pre class="literal-block">
-$ cd ~/<tt class="docutils literal">boost_1_37_0</tt>
+$ cd ~/<tt class="docutils literal">boost_1_38_0</tt>
$ bjam --build-dir=/tmp/build-boost --toolset=gcc stage
</pre>
-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``â€.
+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">--build-type=complete</tt>â€.



@@ -461,7 +461,7 @@
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 â€œ<tt class="docutils literal">>build.log 2>&1</tt>â€ to your command line.
</div>
</div>
</div>
@@ -544,14 +544,14 @@
<ol class="upperalpha">
<li>You can specify the full path to each library:
<pre class="literal-block">
-$ c++ -I path/to/<tt class="docutils literal">boost_1_37_0</tt> example.cpp -o example \
+$ c++ -I path/to/<tt class="docutils literal">boost_1_38_0</tt> example.cpp -o example \
 ~/boost/lib/libboost_regex-gcc34-mt-d-1_36.a
</pre>
</li>
<li>You can separately specify a directory to search (with <tt class="docutils literal">-L</tt>directory) and a library name to search for (with <tt class="docutils literal">-l</tt>library,<a class="footnote-reference" href="#lowercase-l" id="id12">2</a> dropping the filename's leading <tt class="docutils literal">lib</tt> and trailing
suffix (<tt class="docutils literal">.a</tt> in this case):
<pre class="literal-block">
-$ c++ -I path/to/<tt class="docutils literal">boost_1_37_0</tt> example.cpp -o example \
+$ c++ -I path/to/<tt class="docutils literal">boost_1_38_0</tt> example.cpp -o example \
 -L~/boost/lib/ -lboost_regex-gcc34-mt-d-1_36
</pre>
As you can see, this method is just as terse as method A for one

Modified: trunk/more/getting_started/windows.html
==============================================================================
--- trunk/more/getting_started/windows.html (original)
+++ trunk/more/getting_started/windows.html 2008-11-03 10:38:36 EST (Mon, 03 Nov 2008)
@@ -72,7 +72,7 @@
binaries when given the option.
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&package_id=8041"><tt class="docutils literal">boost_1_37_0</tt><tt class="docutils literal">.7z</tt></a> or <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal">boost_1_37_0</tt><tt class="docutils literal">.zip</tt></a> and unpack it to install a complete Boost
+download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal">boost_1_38_0</tt><tt class="docutils literal">.7z</tt></a> or <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal">boost_1_38_0</tt><tt class="docutils literal">.zip</tt></a> and unpack it to install a complete Boost
distribution.<a class="footnote-reference" href="#zip" id="id2">1</a>


@@ -82,7 +82,7 @@
<h1><a class="toc-backref" href="#id27">2   The Boost Distribution</a></h1>
This is a sketch of the resulting directory structure:
<pre class="literal-block">
-boost_1_37_0\ .................The â€œboost root directoryâ€
+boost_1_38_0\ .................The â€œboost root directoryâ€
 index.htm .........A copy of www.boost.org starts here
 boost\ .........................All Boost Header files
 lib\ .....................precompiled library binaries
@@ -127,7 +127,7 @@
</div>
It's important to note the following:
<ol class="arabic" id="boost-root-directory">
-<li>The path to the boost root directory (often <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_37_0</tt>) is
+<li>The path to the boost root directory (often <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_38_0</tt>) is
sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and
mailing lists .
</li>
@@ -251,7 +251,7 @@
</pre>
followed by Return. For example,
<pre class="literal-block">
-cd <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_37_0</tt>
+cd <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_38_0</tt>
</pre>
Long commands can be continued across several lines by typing a
caret (<tt class="docutils literal">^</tt>) at the end of all but the last line. Some examples
@@ -276,7 +276,7 @@
<li>In Configuration Properties > C/C++ > General > Additional Include
Directories, enter the path to the Boost root directory, for example
<blockquote>
-<tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_37_0</tt>
+<tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_38_0</tt>
</blockquote>
</li>
<li>In Configuration Properties > C/C++ > Precompiled Headers, change
@@ -314,7 +314,7 @@
directory</a> to a suitable location for creating some temporary
files and type the following command followed by the Return key:
<pre class="literal-block">
-cl /EHsc /I path\to\<tt class="docutils literal">boost_1_37_0</tt> path\to\example.cpp
+cl /EHsc /I path\to\<tt class="docutils literal">boost_1_38_0</tt> path\to\example.cpp
</pre>
To test the result, type:
<pre class="literal-block">
@@ -345,7 +345,7 @@
<h2><a class="toc-backref" href="#id34">5.1   Install Visual Studio Binaries</a></h2>
The installers supplied by BoostPro Computing will download and
install pre-compiled binaries into the <tt class="docutils literal">lib\</tt> subdirectory of the
-boost root, typically <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_37_0</tt><tt class="docutils literal">\lib\</tt>. If you installed
+boost root, typically <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_38_0</tt><tt class="docutils literal">\lib\</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
step. Otherwise, please run the installer again and install them
now.
@@ -497,8 +497,8 @@
</pre>
For example, your session might look like this:<a class="footnote-reference" href="#continuation" id="id13">4</a>
<pre class="literal-block">
-C:\WINDOWS> cd <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_37_0</tt>
-<tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_37_0</tt>> bjam ^
+C:\WINDOWS> cd <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_38_0</tt>
+<tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_38_0</tt>> bjam ^
More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
More? --toolset= --build-type=complete msvc stage
</pre>
@@ -537,7 +537,7 @@
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 â€œ<tt class="docutils literal">>build.log 2>&1</tt>â€ to your command line.
</div>
</div>
</div>
@@ -637,7 +637,7 @@
select Properties from the resulting pop-up menu</li>
<li>In Configuration Properties > Linker > Additional Library
Directories, enter the path to the Boost binaries,
-e.g. <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_37_0</tt><tt class="docutils literal">\lib\</tt>.</li>
+e.g. <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_38_0</tt><tt class="docutils literal">\lib\</tt>.</li>
<li>From the Build menu, select Build Solution.</li>
</ol>
<a class="reference internal" href="#test-your-program">skip to the next step</a>
@@ -647,10 +647,10 @@
For example, we can compile and link the above program from the
Visual C++ command-line by simply adding the bold text below to
the command line we used earlier, assuming your Boost binaries are
-in <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_37_0</tt><tt class="docutils literal">\lib</tt>:
+in <tt class="docutils literal">C:\Program Files\boost\</tt><tt class="docutils literal">boost_1_38_0</tt><tt class="docutils literal">\lib</tt>:
<pre class="literal-block">
-cl /EHsc /I path\to\<tt class="docutils literal">boost_1_37_0</tt> example.cpp ^
- /link /LIBPATH: C:\Program Files\boost\boost_1_37_0\lib
+cl /EHsc /I path\to\<tt class="docutils literal">boost_1_38_0</tt> example.cpp ^
+ /link /LIBPATH: C:\Program Files\boost\boost_1_38_0\lib
</pre>
</div>
<div class="section" id="library-naming">
@@ -805,7 +805,7 @@
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
<tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td>We recommend
-downloading <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal">boost_1_37_0</tt><tt class="docutils literal">.7z</tt></a> and using <a class="reference external" href="http://www.7-zip.org">7-Zip</a> to decompress
+downloading <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal">boost_1_38_0</tt><tt class="docutils literal">.7z</tt></a> and using <a class="reference external" href="http://www.7-zip.org">7-Zip</a> to decompress
it. We no longer recommend .zip files for Boost because they are twice
as large as the equivalent .7z files. We don't recommend using Windows'
built-in decompression as it can be painfully slow for large archives.</td></tr>

Next message: asutton_at_[hidden]: "[Boost-commit] svn:boost r49563 - in trunk: boost/graph libs/graph/test"
Previous message: asutton_at_[hidden]: "[Boost-commit] svn:boost r49561 - in trunk: boost/graph libs/graph/doc libs/graph/test"

Date view	Thread view	Subject view	Author view

Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk