Fix thanks to "Kevin S. Van Horn" <kvanhorn@ksvanhorn.com>

[SVN r16313]
This commit is contained in:
Dave Abrahams 2002-11-18 14:28:21 +00:00
parent 016de73bd8
commit 87b63053ee

View File

@ -1,165 +1,177 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Boost Download and Installation</title>
</head>
<head>
<meta name="generator" content=
"HTML Tidy for Windows (vers 1st August 2002), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<body bgcolor="#FFFFFF" text="#000000">
<title>Boost Download and Installation</title>
</head>
<table border="1" bgcolor="#007F7F" cellpadding="2">
<body bgcolor="#FFFFFF" text="#000000">
<table border="1" bgcolor="#007F7F" cellpadding="2">
<tr>
<td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" width="277" height="86"></td>
<td><a href="../index.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>Home</big></font></a></td>
<td><a href="../libs/libraries.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>Libraries</big></font></a></td>
<td><a href="../people/people.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>People</big></font></a></td>
<td><a href="faq.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>FAQ</big></font></a></td>
<td><a href="index.htm"><font face="Arial,Helvetica" color="#FFFFFF"><big>More</big></font></a></td>
<td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt=
"c++boost.gif (8819 bytes)" width="277" height="86"></td>
<td><a href="../index.htm"><font face="Arial,Helvetica" color=
"#FFFFFF"><big>Home</big></font></a></td>
<td><a href="../libs/libraries.htm"><font face="Arial,Helvetica"
color="#FFFFFF"><big>Libraries</big></font></a></td>
<td><a href="../people/people.htm"><font face="Arial,Helvetica"
color="#FFFFFF"><big>People</big></font></a></td>
<td><a href="faq.htm"><font face="Arial,Helvetica" color=
"#FFFFFF"><big>FAQ</big></font></a></td>
<td><a href="index.htm"><font face="Arial,Helvetica" color=
"#FFFFFF"><big>More</big></font></a></td>
</tr>
</table>
</table>
<h1>Boost Download and Installation</h1>
<h1>Boost Download and Installation</h1>
The boost libraries are intended for easy download and <a href=
"#Installation">installation</a>; many libraries require nothing more
that downloading and unpacking to be ready for use, including full
documentation.&nbsp; When required, see <a href=
"../tools/build/index.html">Building Boost Libraries</a> to create object
libraries.
The boost libraries are intended for easy download and <a href="#Installation">installation</a>;
many libraries require nothing more that downloading and unpacking to be ready
for use, including full documentation.&nbsp; When required, see <a href="../tools/build/index.html">Building
Boost Libraries</a> to create object libraries.
<h2>Download</h2>
The boost libraries are available in various formats:
<h2>Download</h2>
The boost libraries are available in various formats:
<ul>
<li><a href="http://boost.sourceforge.net/release/">HTTP download</a> all of Boost as a single archive
file (<a href="#.zip">.zip</a> or <a href="#.tar.gz">.tar.gz</a>) file from our
SourceForge HTTP site. Older versions also available. (This option is
suggested first since it doesn't count against our web site host's monthly
fee.)</li>
</ul>
<ul>
<li><a href="../boost_all.zip">ZIP download</a> all of Boost as a single archive
file from our web site.</li>
</ul>
<ul>
<li><a href="../boost_all.tar.gz">TAR.GZ download</a> all of Boost as a single archive
file from our web site.</li>
</ul>
<ul>
<li><a href="#CVS">Command line, GUI</a>, or <a href="#Browser">browser</a> access
to Boost's <a href="http://sourceforge.net/cvs/?group_id=7586">CVS repository</a>.</li>
</ul>
<ul>
<li>Download individual files from links in the documentation on the web
site.&nbsp; Because of the number of files involved, and <a href="../libs/hdr_depend.html">header
dependencies</a>, this option usually isn't very useful.</li>
</ul>
<ul>
<li><a href="http://boost.sourceforge.net/release/">HTTP download</a>
all of Boost as a single archive file (<a href="#.zip">.zip</a> or <a
href="#.tar.gz">.tar.gz</a>) file from our SourceForge HTTP site. Older
versions also available. (This option is suggested first since it
doesn't count against our web site host's monthly fee.)</li>
</ul>
<h3><a name=".zip">.zip</a> file</h3>
<ul>
<li><a href="../boost_all.zip">ZIP download</a> all of Boost as a
single archive file from our web site.</li>
</ul>
The .zip format is widely supported by both free decoders and
commercial compress/archive utilities. If you don't already have a
.zip file decoder, download one from the
<a href="http://www.info-zip.org/">Info-ZIP</a>
web site, which supplies versions for many operating systems.
<p>
Text file line endings in the .zip file are as supplied by each library
developer.&nbsp; This works fine for Windows, but not for Unix/Linux.&nbsp; The
.tar.gz file supplies Unix/Linux friendly line endings.
<ul>
<li><a href="../boost_all.tar.gz">TAR.GZ download</a> all of Boost as a
single archive file from our web site.</li>
</ul>
<ul>
<li><a href="#CVS">Command line, GUI</a>, or <a href=
"#Browser">browser</a> access to Boost's <a href=
"http://sourceforge.net/cvs/?group_id=7586">CVS repository</a>.</li>
</ul>
<h3><a name=".tar.gz">.tar.gz</a> file</h3>
<ul>
<li>Download individual files from links in the documentation on the
web site.&nbsp; Because of the number of files involved, and <a href=
"../libs/hdr_depend.html">header dependencies</a>, this option usually
isn't very useful.</li>
</ul>
The .tar.gz format is widely supported on Unix/Linux platforms. Some
Windows compress/archive utilities can read the format as well.&nbsp; Because
the gzip format compresses the archive as a single file rather than compressing
each file individually, the .tar.gz file is smaller that the .zip file.
<p>Text file line endings in the .tar.gz file have been converted to newlines
for ease of use on Unix/Linux platforms.</p>
<h3><a name=".zip">.zip</a> file</h3>
The .zip format is widely supported by both free decoders and commercial
compress/archive utilities. If you don't already have a .zip file
decoder, download one from the <a href=
"http://www.info-zip.org/">Info-ZIP</a> web site, which supplies versions
for many operating systems.
<h2>Boost <a name="CVS">CVS</a> Repository</h2>
<p>Text file line endings in the .zip file are as supplied by each
library developer.&nbsp; This works fine for Windows, but not for
Unix/Linux.&nbsp; The .tar.gz file supplies Unix/Linux friendly line
endings.</p>
<p>All Boost files, including the entire distribution tree including web site
HTML is maintained in a CVS repository.</p>
<h3><a name=".tar.gz">.tar.gz</a> file</h3>
The .tar.gz format is widely supported on Unix/Linux platforms. Some
Windows compress/archive utilities can read the format as well.&nbsp;
Because the gzip format compresses the archive as a single file rather
than compressing each file individually, the .tar.gz file is smaller that
the .zip file.
<h3>Boost CVS access via command line or graphical clients</h3>
<p>Text file line endings in the .tar.gz file have been converted to
newlines for ease of use on Unix/Linux platforms.</p>
For those who have CVS clients installed, the libraries are also available from
the public <a href="http://sourceforge.net/cvs/?group_id=7586">Boost CVS
repository</a>. Free command line clients (often already installed on Linux/Unix
systems) are available at the <a href="http://www.cvshome.org/">CVS home page</a>,
and free GUI clients are also available for Windows, Mac, and other systems from
<a href="http://www.cvsgui.org/">CvsGui.org</a>.<p>The general procedure for
command-line clients is something like this: </p>
<blockquote>
<code>
cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost login
</code>
<br>
[Hit &lt;return&gt; when it asks for a password]
<br>
<code>
cvs -z3 -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost checkout boost
<br>
cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost logout
</code>
</blockquote>
<h2>Boost <a name="CVS">CVS</a> Repository</h2>
Read the manual for your CVS client for further information.
<p>
This access is read-only; if you are a library author and wish to have
CVS write access, please contact one of the
<a href="mailto:boost-owner@yahoogroups.com">moderators</a>.
<p>All Boost files, including the entire distribution tree including web
site HTML is maintained in a CVS repository.</p>
<h3>Boost CVS access via command line or graphical clients</h3>
For those who have CVS clients installed, the libraries are also
available from the public <a href=
"http://sourceforge.net/cvs/?group_id=7586">Boost CVS repository</a>.
Free command line clients (often already installed on Linux/Unix systems)
are available at the <a href="http://www.cvshome.org/">CVS home page</a>,
and free GUI clients are also available for Windows, Mac, and other
systems from <a href="http://www.cvsgui.org/">CvsGui.org</a>.
<h3>Boost CVS access via web <a name="Browser">Browser</a></h3>
<p>The general procedure for command-line clients is something like
this:</p>
For access to the CVS archive from any modern web browser, you can
also use the <a
href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/">web
browser&nbsp; interface</a>.&nbsp; Try one of the color diffs to see
how a file has changed over time.
<blockquote>
<code>cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost
login</code><br>
[Hit &lt;return&gt; when it asks for a password]<br>
<code>cvs -z3
-d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost checkout
boost<br>
cvs -d:pserver:anonymous@cvs.boost.sourceforge.net:/cvsroot/boost
logout</code>
</blockquote>
Read the manual for your CVS client for further information.
<p>This access is read-only; if you are a library author and wish to have
CVS write access, please contact one of the <a href=
"mailto:boost-owner@yahoogroups.com">moderators</a>.</p>
<h3>Boost CVS access via web <a name="Browser">Browser</a></h3>
For access to the CVS archive from any modern web browser, you can also
use the <a href=
"http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/">web
browser&nbsp; interface</a>.&nbsp; Try one of the color diffs to see how
a file has changed over time.
<h2><a name="Installation">Installation</a></h2>
<h2><a name="Installation">Installation</a></h2>
Boost does not yet have a standardized installation process. There has
been some interest in developing one; as of this writing <a href=
"../people/william_kempf.htm">Bill Kempf</a> has volunteered to
coordinate and is gathering volunteers. If you have expertise in this
area (particularly cross-platform expertise), and you would like to
contribute, please announce your availability on the <a href=
"http://lists.boost.org/mailman/listinfo.cgi/boost-install">Boost
Install</a> mailing list.
Boost does not yet have a standardized installation process. There has
been some interest in developing one; as of this writing <a
href="../people/william_kempf.htm">Bill Kempf</a> has volunteered to
coordinate and is gathering volunteers. If you have expertise in this
area (particularly cross-platform expertise), and you would like to
contribute, please announce your availability on the
<a
href="http://lists.boost.org/mailman/listinfo.cgi/boost-install">Boost
Install</a> mailing list.
<p>That said, preparing to use Boost in a development project is
relatively straightforward. Most boost libraries are implemented entirely
within their header files. The only preparation for their use is to add
the boost root directory to your compiler's list of
<code>#include&lt;...&gt;</code> search paths. For example, using Windows
2000, if you have unzipped release 1.28.0 from boost_all.zip into the top
level directory of your C drive, adding '-Ic:/boost_1_28_0' to the
command line of most compilers is sufficient.</p>
<p>
<p>The <a href="../libs/python/doc/index.html">Python</a>, <a href=
"../libs/regex/index.htm">Regex</a>, and <a href=
"../libs/thread/doc/index.html">Threads</a> libraries are implemented in
part as separate source files, and thus require compilation before use.
See <a href="../tools/build/index.html">Building Boost Libraries</a> for
an automatic tool to prepare such libraries. Some of the individual
libraries also include make and/or project files for various compilers,
but <em>every</em> library with a built component includes the neccessary
<code>Jamfile</code> for building with <a href=
"../tools/build/index.html">Boost.Build</a>, our standard build tool.</p>
<hr>
Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->18
November, 2002<!--webbot bot="Timestamp" endspan i-checksum="34416" -->
That said, preparing to use Boost in a development project is
relatively straightforward. Most boost libraries are implemented
entirely within their header files. The only preparation for their
use is to add the boost root directory to your compiler's list of
<code>#include&lt;...&gt;</code> search paths. For example,
using Windows 2000, if you have unzipped release 1.28.0 from
boost_all.zip into the top level directory of your C drive, adding
'-Ic:/boost_1_28_0' to the command line of most compilers is
sufficient.
<p>
The <a href="../libs/python/doc/index.html">Python</a>, <a
href="../libs/regex/index.htm">Regex</a>, and <a
href="../libs/thread/doc/index.html">Threads</a> libraries are
implemented in part as separate source files, and thus require
compilation before use. See <a
href="../tools/build/index.html">Building Boost Libraries</a> for an
automatic tool to prepare such libraries. Some of the individual
libraries also include make and/or project files for various
compilers, but every library also
<p>
<hr>
Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->06 August, 2002<!--webbot bot="Timestamp" endspan i-checksum="34416" -->
<p>Written by&nbsp; <a href="../people/jens_maurer.htm">Jens Maurer</a>
2001-02-11</p>
</body>
<p>Written by&nbsp; <a href="../people/jens_maurer.htm">Jens Maurer</a>
2001-02-11</p>
</body>
</html>