boost/more
1
0
Fork 0
mirror of https://github.com/boostorg/more.git synced 2025-03-28 14:00:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

Place emphasis on getting prebuilts

Browse Source 
[SVN r23340]
This commit is contained in:
Dave Abrahams 2004-07-04 22:18:00 +00:00
parent 9ac3e12317
commit 6a6ed69ff0
1 changed files with 1084 additions and 990 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

582
getting_started.html
View File

@ -2,16 +2,19 @@
<html> <html>
<head> <head>
<title>Getting Started</title>
<meta name="generator" content= <meta name="generator" content=
"Microsoft FrontPage 5.0"> "HTML Tidy for Cygwin (vers 1st April 2002), see www.w3.org">
<title>Getting Started</title>
<meta name="generator" content="Microsoft FrontPage 5.0">
<meta http-equiv="Content-Language" content="en-us"> <meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../boost.css"> <link rel="stylesheet" type="text/css" href="../boost.css">
</head> </head>
<body bgcolor="#FFFFFF" text="#000000"> <body bgcolor="#FFFFFF" text="#000000">
<table summary="" width="100%" border="0" cellspacing="0" cellpadding="0"> <table summary="" width="100%" border="0" cellspacing="0" cellpadding=
"0">
<tr valign="top"> <tr valign="top">
<td valign="top" align="left"><img src="../c%2B%2Bboost.gif" alt= <td valign="top" align="left"><img src="../c%2B%2Bboost.gif" alt=
"c++boost.gif (8819 bytes)" width="277" height="86"></td> "c++boost.gif (8819 bytes)" width="277" height="86"></td>
@ -24,7 +27,8 @@
<tr> <tr>
<td bgcolor="#DDDDDD"> <td bgcolor="#DDDDDD">
<p>.&nbsp;<a href="../index.htm">Home</a><br> <p>.&nbsp;<a href="../index.htm">Home</a><br>
.&nbsp;<a href="../libs/libraries.htm">Libraries</a><br> .&nbsp;<a href=
"../libs/libraries.htm">Libraries</a><br>
.&nbsp;<a href="../people/people.htm">People</a><br> .&nbsp;<a href="../people/people.htm">People</a><br>
.&nbsp;<a href="faq.htm">FAQ</a><br> .&nbsp;<a href="faq.htm">FAQ</a><br>
.&nbsp;<a href="index.htm">More</a></p> .&nbsp;<a href="index.htm">More</a></p>
@ -74,9 +78,9 @@
<h2><a name="Introduction">Introduction</a></h2> <h2><a name="Introduction">Introduction</a></h2>
<p>These instructions are intended to help you get started using the Boost <p>These instructions are intended to help you get started using the
Libraries. This walks you through getting, building, and installing the Boost Libraries. This walks you through getting, building, and installing
libraries. To summarize these are the steps to get Boost built and the libraries. To summarize these are the steps to get Boost built and
installed:</p> installed:</p>
<ol> <ol>
@ -93,48 +97,51 @@
<h2><a name="Download"></a>Download</h2> <h2><a name="Download"></a>Download</h2>
<table summary="" width="100%" border="0" cellspacing="2" cellpadding="2"> <table summary="" width="100%" border="0" cellspacing="2" cellpadding=
"2">
<tr align="left" valign="top"> <tr align="left" valign="top">
<td width="40" align="center" valign="top" bgcolor="#FFFF66"> <td width="40" align="center" valign="top" bgcolor="#FFFF66"><font
<font size="6"><b><a name="step1"></a>1</b></font></td> size="6"><b><a name="step1"></a>1</b></font></td>
<td>The Boost Libraries are distributed through the SourceForge file <td>The Boost Libraries are distributed through the SourceForge file
distribution system. Click here to <b><a href= distribution system. Click here to <b><a href=
"http://sourceforge.net/project/showfiles.php?group_id=7586"><font size="4"> "http://sourceforge.net/project/showfiles.php?group_id=7586"><font
download releases from SourceForge</font></a></b>. And unpack the size="4">download releases from SourceForge</font></a></b>. And
release to a convenient location.</td> unpack the release to a convenient location.</td>
</tr> </tr>
</table> </table>
<p>The Boost release includes all of the libraries and other material from <p>The Boost release includes all of the libraries and other material
the web site. It is available in <a href="#.zip">ZIP</a>, <a href= from the web site. It is available in <a href="#.zip">ZIP</a>, <a href=
"#.tar.gz">TAR.GZ</a>, and <a href="#.tar.gz">TAR.BZ2</a> formats. Past "#.tar.gz">TAR.GZ</a>, and <a href="#.tar.gz">TAR.BZ2</a> formats. Past
releases are also available.</p>It is also possible to download current releases are also available.</p>
snapshots of work-in-progress from Boost's <a href="#CVS">CVS It is also possible to download current snapshots of work-in-progress
repository</a>. from Boost's <a href="#CVS">CVS repository</a>.
<h3><a name=".zip">.zip</a> file</h3>The .zip format is widely supported by <h3><a name=".zip">.zip</a> file</h3>
both free decoders and commercial compress/archive utilities. If you don't The .zip format is widely supported by both free decoders and commercial
already have a .zip file decoder, download one from the <a href= 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 "http://www.info-zip.org/">Info-ZIP</a> web site, which supplies versions
for many operating systems. for many operating systems.
<p>Text file line endings in the .zip file are as supplied by each library <p>Text file line endings in the .zip file are as supplied by each
developer.&nbsp; This works fine for Windows, but not for Unix/Linux.&nbsp; library developer.&nbsp; This works fine for Windows, but not for
The .tar.gz and .tar.bz2 files supply Unix/Linux friendly line endings.</p> Unix/Linux.&nbsp; The .tar.gz and .tar.bz2 files supply Unix/Linux
friendly line endings.</p>
<h3><a name=".tar.gz">.tar.gz</a> and .tar.bz2 files</h3> <h3><a name=".tar.gz">.tar.gz</a> and .tar.bz2 files</h3>
<p>The .tar.gz format is widely supported on Unix/Linux platforms. Some <p>The .tar.gz format is widely supported on Unix/Linux platforms. Some
Windows compress/archive utilities can read the format as well.&nbsp; Windows compress/archive utilities can read the format as well.&nbsp;
Because the gzip format compresses the archive as a single file rather than Because the gzip format compresses the archive as a single file rather
compressing each file individually, the .tar.gz file is smaller that the than compressing each file individually, the .tar.gz file is smaller that
.zip file.</p> the .zip file.</p>
<p>The .tar.bz2 format is becoming widely available on Unix/Linux platforms <p>The .tar.bz2 format is becoming widely available on Unix/Linux
and is built into many tar utilities. This format differs for the .tar.gz platforms and is built into many tar utilities. This format differs for
format in the compression used, which is considerably better and therefore the .tar.gz format in the compression used, which is considerably better
creates smaller files.</p> and therefore creates smaller files.</p>
<p>Text file line endings in the .tar.gz and .tar.bz2 files have been <p>Text file line endings in the .tar.gz and .tar.bz2 files have been
converted to newlines for ease of use on Unix/Linux platforms.</p> converted to newlines for ease of use on Unix/Linux platforms.</p>
@ -142,87 +149,95 @@
<h3>Boost <a name="CVS">CVS</a> Repository</h3> <h3>Boost <a name="CVS">CVS</a> Repository</h3>
<p>All Boost files, including the entire distribution tree including web <p>All Boost files, including the entire distribution tree including web
site HTML is maintained in a CVS repository. Command line, GUI, or browser site HTML is maintained in a CVS repository. Command line, GUI, or
access is available.</p> browser access is available.</p>
<h4>Boost CVS access via command line or graphical clients</h4>For those <h4>Boost CVS access via command line or graphical clients</h4>
who have CVS clients installed, the libraries are also available from the For those who have CVS clients installed, the libraries are also
public <a href="http://sourceforge.net/cvs/?group_id=7586">Boost CVS available from the public <a href=
repository</a>. Free command line clients (often already installed on "http://sourceforge.net/cvs/?group_id=7586">Boost CVS repository</a>.
Linux/Unix systems) are available for many systems, and free GUI clients Free command line clients (often already installed on Linux/Unix systems)
are available for Windows, Mac, and other systems. are available for many systems, and free GUI clients are available for
Windows, Mac, and other systems.
<p>See the much improved <a href= <p>See the much improved <a href=
"http://sourceforge.net/docman/?group_id=1">CVS documentation</a> (Section "http://sourceforge.net/docman/?group_id=1">CVS documentation</a>
F) from SourceForge, which includes links to the home pages for various GUI (Section F) from SourceForge, which includes links to the home pages for
and command line clients.</p> various GUI and command line clients.</p>
<p>The general procedure for command-line clients is something like <p>The general procedure for command-line clients is something like
this:</p> this:</p>
<blockquote> <blockquote>
<code>cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login</code><br> <code>cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost
login</code><br>
[Hit &lt;return&gt; when it asks for a password]<br> [Hit &lt;return&gt; when it asks for a password]<br>
<code>cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost checkout boost</code><br> <code>cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost
<code>cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost logout</code> checkout boost</code><br>
</blockquote>Read the manual for your CVS client for further information. <code>cvs -d:pserver:anonymous@cvs.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 <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= CVS write access, please contact one of the <a href=
"moderators.html">moderators</a>.</p> "moderators.html">moderators</a>.</p>
<h4>Boost CVS access via web <a name="Browser">Browser</a></h4>For access <h4>Boost CVS access via web <a name="Browser">Browser</a></h4>
to the CVS archive from any modern web browser, you can also use the For access to the CVS archive from any modern web browser, you can also
<a use the <a href=
href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/">web "http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/">web
browser&nbsp; interface</a>.&nbsp; Try one of the color diffs to see browser&nbsp; interface</a>.&nbsp; Try one of the color diffs to see how
how a file has changed over time. <b>Note:</b> this interface is only suitable a file has changed over time. <b>Note:</b> this interface is only
for viewing individual files and their revision histories. If you suitable for viewing individual files and their revision histories. If
need an image of the whole CVS tree, <a you need an image of the whole CVS tree, <a href=
href="http://www.boost-consulting.com">Boost Consulting</a> provides "http://www.boost-consulting.com">Boost Consulting</a> provides an hourly
an hourly <a <a href="http://www.boost-consulting.com/boost.tar.bz2">snapshot in
href="http://www.boost-consulting.com/boost.tar.bz2">snapshot in
.tar.bz2 format</a>. .tar.bz2 format</a>.
<h4><a name="generated">Documentation</a> generated from BoostBook <h4><a name="generated">Documentation</a> generated from BoostBook in
in CVS</h4> CVS</h4>
<p>Some of the Boost documentation is generated from <a <p>Some of the Boost documentation is generated from <a href=
href="../doc/html/boostbook.html">BoostBook XML</a> source stored in "../doc/html/boostbook.html">BoostBook XML</a> source stored in the CVS
the CVS repository, and will not appear directly in the CVS tree as repository, and will not appear directly in the CVS tree as readable
readable HTML. View a nightly build of the generated HTML on the <a HTML. View a nightly build of the generated HTML on the <a href=
href="http://www.boost.org/regression-logs/cs-win32_metacomm/doc/html/libraries.html">Nightly "http://www.boost.org/regression-logs/cs-win32_metacomm/doc/html/libraries.html">
Generated Documentation</a> page. Where generated HTML is missing from the Nightly Generated Documentation</a> page. Where generated HTML is missing
CVS tree, an attempt has been made to include redirection to this from the CVS tree, an attempt has been made to include redirection to
nightly build, but if you are away from an internet connection you this nightly build, but if you are away from an internet connection you
may want to download the generated documentation archive from the may want to download the generated documentation archive from the
aforementioned page so you can browse those documents offline. aforementioned page so you can browse those documents offline.</p>
<h2><a name="Preparation"></a>Preparation</h2> <h2><a name="Preparation"></a>Preparation</h2>
<p>The recommended way to build and install the Boost Libraries is to use <p>The recommended way to build and install the Boost Libraries is to use
<a href="../tools/build/v1/build_system.htm">Boost.Build</a>, the Boost <a href="../tools/build/v1/build_system.htm">Boost.Build</a>, the Boost
Build system. The rest of these instructions explain that use, but it is up Build system. The rest of these instructions explain that use, but it is
to you to use this method, or not. Note that some of the libraries also up to you to use this method, or not. Note that some of the libraries
include non Boost.Build makefiles and/or project files. But all include the also include non Boost.Build makefiles and/or project files. But all
needed files for building with Boost.Build.</p> include the needed files for building with Boost.Build.</p>
<table summary="" width="100%" border="0" cellspacing="2" cellpadding="2"> <table summary="" width="100%" border="0" cellspacing="2" cellpadding=
"2">
<tr align="left" valign="top"> <tr align="left" valign="top">
<td width="40" align="center" valign="top" bgcolor="#FFFF66"> <td width="40" align="center" valign="top" bgcolor="#FFFF66"><font
<font size="6"><b><a name="step2"></a>2</b></font></td> size="6"><b><a name="step2"></a>2</b></font></td>
<td>The build system uses <a href= <td>The build system uses <a href=
"../tools/build/jam_src/index.html">Boost.Jam</a>, an extension of the "../tools/build/jam_src/index.html">Boost.Jam</a>, an extension of
<a href="http://www.perforce.com/jam/jam.html">Perforce Jam</a> the <a href="http://www.perforce.com/jam/jam.html">Perforce Jam</a>
portable <i>make</i> replacement. You can either <a href= portable <i>make</i> replacement. The recommended way to get
"../tools/build/jam_src/index.html#building_bjam">build this Boost.Jam if you are using a Boost distribution is to <strong><a
yourself</a>, it's included with the distribution. Or obtain a href=
<strong><a href= "http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941">
"http://sourceforge.net/project/showfiles.php?group_id=7586"><font size="4"> download a prebuilt executable</a></strong> from SourceForge. If a prebuilt
prebuilt from SourceForge</font></a></strong>. To install Boost.Jam, executable is not provided for your platform or you
copy the <tt>bjam</tt> executable to a location accessible in your are using Boost's sources in an unreleased state, it may be neccessary to
<tt>PATH</tt>.</td> <a href="../tools/build/jam_src/index.html#building_bjam">build
<tt>bjam</tt> from sources</a> included in the Boost source tree. To
install Boost.Jam, copy the <tt>bjam</tt> executable to a location
accessible in your <tt>PATH</tt>.</td>
</tr> </tr>
</table> </table>
@ -233,208 +248,273 @@
of two ways:</p> of two ways:</p>
<ol> <ol>
<li>The user sets up all of the environment for each toolset he <li>The user sets up all of the environment for each toolset he wants
wants to use in the normal way. For example, for Microsoft VC++, to use in the normal way. For example, for Microsoft VC++, ...VC98/Bin
...VC98/Bin or .../VC7/Bin is in the PATH environment variable, or .../VC7/Bin is in the PATH environment variable, VCVARS32.BAT or
VCVARS32.BAT or VSVARS32.BAT has been invoked, etc. For Metrowerks VSVARS32.BAT has been invoked, etc. For Metrowerks CodeWarrior,
CodeWarrior, cwenv.bat or equivalent has been called and ...Other cwenv.bat or equivalent has been called and ...Other Metrowerks
Metrowerks Tools/Command Line Tools is in the path. Many Unix Tools/Command Line Tools is in the path. Many Unix operating systems
operating systems come preconfigured this way and require no user come preconfigured this way and require no user intervention.<br>
intervention.<br> <br>
<br></li> </li>
<li>The user doesn't want his environment cluttered with settings or has <li>The user doesn't want his environment cluttered with settings or
nonstandard installations for some of his tools. Instead, he or she sets has nonstandard installations for some of his tools. Instead, he or she
variables which point to the toolset installation directories, either in sets variables which point to the toolset installation directories,
the command shell environment or on the <code>bjam</code> command-line. either in the command shell environment or on the <code>bjam</code>
These variables are used by the build system to locate the tools and command-line. These variables are used by the build system to locate
invoke the necessary setup. To set the variables on the <tt>bjam</tt> the tools and invoke the necessary setup. To set the variables on the
command-line you use the "<tt>-s</tt>" option. For example:<br> <tt>bjam</tt> command-line you use the "<tt>-s</tt>" option. For
example:<br>
<br> <br>
<tt>bjam "-sGCC_ROOT=/usr/local/gcc-3.3.2"</tt><br> <tt>bjam "-sGCC_ROOT=/usr/local/gcc-3.3.2"</tt><br>
<br> <br>
Some variables, like the toolset <tt>TOOLS</tt> variable, can accept Some variables, like the toolset <tt>TOOLS</tt> variable, can accept
multiple values separated by spaces. Others, like the path above, can multiple values separated by spaces. Others, like the path above, can
contain spaces. For such circumstances you should use quotes appropriate contain spaces. For such circumstances you should use quotes
for your command interpreter.<br></li> appropriate for your command interpreter.<br>
</li>
</ol> </ol>
<h3><a name="Tools">Supported Toolsets</a></h3> <h3><a name="Tools">Supported Toolsets</a></h3>
<table summary="" width="100%" border="0" cellspacing="2" cellpadding="2"> <table summary="" width="100%" border="0" cellspacing="2" cellpadding=
"2">
<tr align="left" valign="top"> <tr align="left" valign="top">
<td width="40" align="center" valign="top" bgcolor="#FFFF66"> <td width="40" align="center" valign="top" bgcolor="#FFFF66"><font
<font size="6"><b><a name="step3"></a>3</b></font></td> size="6"><b><a name="step3"></a>3</b></font></td>
<td>The following toolsets are supported by Boost.Build. For <td>The following toolsets are supported by Boost.Build. For
information about <a href="#Configuring">configuring</a> each toolset, information about <a href="#Configuring">configuring</a> each
click its name in the leftmost column.</td> toolset, click its name in the leftmost column.</td>
</tr> </tr>
</table><br> </table>
<br>
<table summary="" border="1" cellpadding="5"> <table summary="" border="1" cellpadding="5">
<tr> <tr>
<td><b>TOOLS Name</b></td> <td><b>TOOLS Name</b></td>
<td><b>Description</b></td> <td><b>Description</b></td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/borland-tools.html"><code>borland</code></a></td> "../tools/build/v1/borland-tools.html"><code>borland</code></a></td>
<td><a href= <td><a href=
"http://www.borland.com/bcppbuilder/freecompiler">Borland</a> C++</td> "http://www.borland.com/bcppbuilder/freecompiler">Borland</a>
C++</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/como-tools.html"><code>como</code></a></td> "../tools/build/v1/como-tools.html"><code>como</code></a></td>
<td><a href="http://www.comeaucomputing.com">Comeau C++</a> compiler front-end
for non-Windows platforms</td> <td><a href="http://www.comeaucomputing.com">Comeau C++</a> compiler
front-end for non-Windows platforms</td>
</tr> </tr>
<tr> <tr>
<td><code><a href= <td><code><a href=
"../tools/build/v1/como-tools.html">como-win32</a></code></td> "../tools/build/v1/como-tools.html">como-win32</a></code></td>
<td><a href="http://www.comeaucomputing.com">Comeau C++</a> compiler front-end
for Windows, using Microsoft <a href= <td><a href="http://www.comeaucomputing.com">Comeau C++</a> compiler
"http://msdn.microsoft.com/visualc/">Visual C++</a>as a back-end.</td> front-end for Windows, using Microsoft <a href=
"http://msdn.microsoft.com/visualc/">Visual C++</a>as a
back-end.</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/cw-tools.html"><code>cw</code></a></td> "../tools/build/v1/cw-tools.html"><code>cw</code></a></td>
<td><a href="http://www.metrowerks.com">Metrowerks CodeWarrior</a> Pro 6.x,
7.x, 8.x, and 9.x command-line tools</td> <td><a href="http://www.metrowerks.com">Metrowerks CodeWarrior</a>
Pro 6.x, 7.x, 8.x, and 9.x command-line tools</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/darwin-tools.html"><code>darwin</code></a></td> "../tools/build/v1/darwin-tools.html"><code>darwin</code></a></td>
<td>Apple Darwin OS hosted GNU <a href= <td>Apple Darwin OS hosted GNU <a href=
"http://developer.apple.com/tools/compilers.html">GCC</a>.</td> "http://developer.apple.com/tools/compilers.html">GCC</a>.</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/edg-tools.html"><code>edg</code></a></td> "../tools/build/v1/edg-tools.html"><code>edg</code></a></td>
<td><a href="http://www.edg.com/">Edison Design Group</a> compiler front-end
(evaluation version)</td> <td><a href="http://www.edg.com/">Edison Design Group</a> compiler
front-end (evaluation version)</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/gcc-tools.html"><code>gcc</code></a></td> "../tools/build/v1/gcc-tools.html"><code>gcc</code></a></td>
<td><a href="http://gcc.gnu.org">GNU GCC</a> on Unix and <a href= <td><a href="http://gcc.gnu.org">GNU GCC</a> on Unix and <a href=
"http://www.cygwin.com">Cygwin</a>.</td> "http://www.cygwin.com">Cygwin</a>.</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/gcc-stlport-tools.html"><code>gcc-stlport</code></a></td> "../tools/build/v1/gcc-stlport-tools.html"><code>gcc-stlport</code></a></td>
<td><a href="http://gcc.gnu.org">GNU GCC</a> on Unix and <a href= <td><a href="http://gcc.gnu.org">GNU GCC</a> on Unix and <a href=
"http://www.cygwin.com">Cygwin</a>, using the <a href= "http://www.cygwin.com">Cygwin</a>, using the <a href=
"http://www.stlport.org">STLport</a> standard library implementation</td> "http://www.stlport.org">STLport</a> standard library
implementation</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/gcc-nocygwin-tools.html"><code>gcc-nocygwin</code></a></td> "../tools/build/v1/gcc-nocygwin-tools.html"><code>gcc-nocygwin</code></a></td>
<td>GNU GCC Cygwin command line compiler tools running in "no-cygwin" mode
(produces commercially redistributable objects)</td> <td>GNU GCC Cygwin command line compiler tools running in "no-cygwin"
mode (produces commercially redistributable objects)</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/intel-linux-tools.html"><code>intel-linux</code></a></td> "../tools/build/v1/intel-linux-tools.html"><code>intel-linux</code></a></td>
<td><a href= <td><a href=
"http://www.intel.com/software/products/compilers/c60l/">Intel C++ for Linux</a></td> "http://www.intel.com/software/products/compilers/c60l/">Intel C++
for Linux</a></td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/intel-win32-tools.html"><code>intel-win32</code></a></td> "../tools/build/v1/intel-win32-tools.html"><code>intel-win32</code></a></td>
<td><a href= <td><a href=
"http://www.intel.com/software/products/compilers/c60/">Intel C++ for Windows</a> "http://www.intel.com/software/products/compilers/c60/">Intel C++ for
using the Dinkumware standard library in the Intel-required Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual Windows</a> using the Dinkumware standard library in the
C++</a> 6 or 7 installation</td> Intel-required Microsoft <a href=
"http://msdn.microsoft.com/visualc/">Visual C++</a> 6 or 7
installation</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/kcc-tools.html"><code>kcc</code></a></td> "../tools/build/v1/kcc-tools.html"><code>kcc</code></a></td>
<td><a href="http://developer.intel.com/software/products/kcc/">KAI C++</a></td>
<td><a href="http://developer.intel.com/software/products/kcc/">KAI
C++</a></td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/kylix-tools.html"><code>kylix</code></a></td> "../tools/build/v1/kylix-tools.html"><code>kylix</code></a></td>
<td><a href="http://www.borland.com/kylix">Borland C++ for Linux (Kylix).</a></td>
<td><a href="http://www.borland.com/kylix">Borland C++ for Linux
(Kylix).</a></td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/mingw-tools.html"><code>mingw</code></a></td> "../tools/build/v1/mingw-tools.html"><code>mingw</code></a></td>
<td>GNU GCC and associated tools in <a href= <td>GNU GCC and associated tools in <a href=
"http://www.mingw.org">MinGW</a> configuration (produces commercially redistributable "http://www.mingw.org">MinGW</a> configuration (produces commercially
objects)</td> redistributable objects)</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/mipspro-tools.html"><code>mipspro</code></a></td> "../tools/build/v1/mipspro-tools.html"><code>mipspro</code></a></td>
<td>SGI <a href= <td>SGI <a href=
"http://www.sgi.com/developers/devtools/languages/mipspro.html">MIPSpro "http://www.sgi.com/developers/devtools/languages/mipspro.html">MIPSpro
C and C++</a></td> C and C++</a></td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/msvc-tools.html"><code>msvc</code></a></td> "../tools/build/v1/msvc-tools.html"><code>msvc</code></a></td>
<td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual C++</a>
version 6 command-line tools. NOTE; For version 7.x (the .NET series) use <td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual
the vc7 or vc7.1 toolsets below.</td> C++</a> version 6 command-line tools. NOTE; For version 7.x (the .NET
series) use the vc7 or vc7.1 toolsets below.</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/msvc-stlport-tools.html"><code>msvc-stlport</code></a></td> "../tools/build/v1/msvc-stlport-tools.html"><code>msvc-stlport</code></a></td>
<td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual C++</a>
version 6 command-line tools, using the <a href= <td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual
"http://www.stlport.org">STLport</a> standard library implementation. NOTE; C++</a> version 6 command-line tools, using the <a href=
For version 7.x (the .NET series) use the vc7-stlport or vc7.1-stlport toolsets "http://www.stlport.org">STLport</a> standard library implementation.
below.</td> NOTE; For version 7.x (the .NET series) use the vc7-stlport or
vc7.1-stlport toolsets below.</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/sunpro-tools.html"><code>sunpro</code></a></td> "../tools/build/v1/sunpro-tools.html"><code>sunpro</code></a></td>
<td><a href= <td><a href=
"http://wwws.sun.com/software/sundev/suncc/index.html">SunPRO C++</a> compiler</td> "http://wwws.sun.com/software/sundev/suncc/index.html">SunPRO C++</a>
compiler</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/tru64cxx-tools.html"><code>tru64cxx</code></a></td> "../tools/build/v1/tru64cxx-tools.html"><code>tru64cxx</code></a></td>
<td><a href="http://www.tru64unix.compaq.com/cplus/">Compaq C++</a> for Tru64
UNIX (versions prior to 6.5)</td> <td><a href="http://www.tru64unix.compaq.com/cplus/">Compaq C++</a>
for Tru64 UNIX (versions prior to 6.5)</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/tru64cxx-tools.html"><code>tru64cxx65</code></a></td> "../tools/build/v1/tru64cxx-tools.html"><code>tru64cxx65</code></a></td>
<td><a href="http://www.tru64unix.compaq.com/cplus/">Compaq C++</a> Version
6.5 for Tru64 UNIX</td> <td><a href="http://www.tru64unix.compaq.com/cplus/">Compaq C++</a>
Version 6.5 for Tru64 UNIX</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/vacpp-tools.html"><code>vacpp</code></a></td> "../tools/build/v1/vacpp-tools.html"><code>vacpp</code></a></td>
<td><a href="http://www-3.ibm.com/software/ad/vacpp/">IBM Visual Age C++</a>
command-line tools</td> <td><a href="http://www-3.ibm.com/software/ad/vacpp/">IBM Visual Age
C++</a> command-line tools</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/vc7-tools.html"><code>vc7</code></a></td> "../tools/build/v1/vc7-tools.html"><code>vc7</code></a></td>
<td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual C++</a>
command-line tools from Visual Studio .NET.</td> <td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual
C++</a> command-line tools from Visual Studio .NET.</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/vc7-stlport-tools.html"><code>vc7-stlport</code></a></td> "../tools/build/v1/vc7-stlport-tools.html"><code>vc7-stlport</code></a></td>
<td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual C++</a>
command-line tools from Visual Studio .NET + STLPort.</td> <td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual
C++</a> command-line tools from Visual Studio .NET + STLPort.</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/vc7.1-tools.html"><code>vc7.1</code></a></td> "../tools/build/v1/vc7.1-tools.html"><code>vc7.1</code></a></td>
<td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual C++</a>
command-line tools from Visual Studio .NET 2003.</td> <td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual
C++</a> command-line tools from Visual Studio .NET 2003.</td>
</tr> </tr>
<tr> <tr>
<td><a href= <td><a href=
"../tools/build/v1/vc7.1-stlport-tools.html"><code>vc7.1-stlport</code></a></td> "../tools/build/v1/vc7.1-stlport-tools.html"><code>vc7.1-stlport</code></a></td>
<td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual C++</a>
command-line tools from Visual Studio .NET 2003 + STLPort.</td> <td>Microsoft <a href="http://msdn.microsoft.com/visualc/">Visual
C++</a> command-line tools from Visual Studio .NET 2003 +
STLPort.</td>
</tr> </tr>
</table> </table>
@ -443,14 +523,15 @@
<p>The common build and install process is driven by the top-level build <p>The common build and install process is driven by the top-level build
file (<a href="../Jamfile">Jamfile</a>).</p> file (<a href="../Jamfile">Jamfile</a>).</p>
<table summary="" width="100%" border="0" cellspacing="2" cellpadding="2"> <table summary="" width="100%" border="0" cellspacing="2" cellpadding=
"2">
<tr align="left" valign="top"> <tr align="left" valign="top">
<td width="40" align="center" valign="top" bgcolor="#FFFF66"> <td width="40" align="center" valign="top" bgcolor="#FFFF66"><font
<font size="6"><b><a name="step4"></a>4</b></font></td> size="6"><b><a name="step4"></a>4</b></font></td>
<td> <td>
<p>First you need to change to the directory where you have the Boost <p>First you need to change to the directory where you have the
distribution you downloaded. For example:</p> Boost distribution you downloaded. For example:</p>
<blockquote> <blockquote>
<p><code>chdir&nbsp;boost-1.31.0</code></p> <p><code>chdir&nbsp;boost-1.31.0</code></p>
@ -459,18 +540,20 @@
</tr> </tr>
</table> </table>
<p>The default build and install attempts to build all available libraries <p>The default build and install attempts to build all available
and install to default locations the libraries and Boost header files. On libraries and install to default locations the libraries and Boost header
Unix systems the default install location is "<tt>/usr/local</tt>", and on files. On Unix systems the default install location is
Windows systems the default is "<tt>C:\Boost</tt>". Within those "<tt>/usr/local</tt>", and on Windows systems the default is
directories libraries are installed to the "<tt>lib</tt>" subdirectory, and "<tt>C:\Boost</tt>". Within those directories libraries are installed to
headers to an "<tt>include/boost-1_31</tt>" subdirectory, the version will the "<tt>lib</tt>" subdirectory, and headers to an
reflect the distribution you are installing.</p> "<tt>include/boost-1_31</tt>" subdirectory, the version will reflect the
distribution you are installing.</p>
<table summary="" width="100%" border="0" cellspacing="2" cellpadding="2"> <table summary="" width="100%" border="0" cellspacing="2" cellpadding=
"2">
<tr align="left" valign="top"> <tr align="left" valign="top">
<td width="40" align="center" valign="top" bgcolor="#FFFF66"> <td width="40" align="center" valign="top" bgcolor="#FFFF66"><font
<font size="6"><b><a name="step5"></a>5</b></font></td> size="6"><b><a name="step5"></a>5</b></font></td>
<td> <td>
Invoke the build system, specifying the <a href= Invoke the build system, specifying the <a href=
@ -481,8 +564,8 @@
<p><code>bjam&nbsp;"-sTOOLS=gcc" install</code></p> <p><code>bjam&nbsp;"-sTOOLS=gcc" install</code></p>
</blockquote> </blockquote>
<p>Or if you are interested only in the built libraries you can have <p>Or if you are interested only in the built libraries you can
them built and collected to a common directory without have them built and collected to a common directory without
installation.</p> installation.</p>
<blockquote> <blockquote>
@ -492,11 +575,11 @@
</tr> </tr>
</table> </table>
<p>The build and install system can be controlled through a set of options <p>The build and install system can be controlled through a set of
similar in style to GNU configure options. The options allow you to, among options similar in style to GNU configure options. The options allow you
other things, change the install location, disable building of libraries, to, among other things, change the install location, disable building of
etc. You can see a summary of the available options by invoking "<tt>bjam libraries, etc. You can see a summary of the available options by
--help</tt>". The full invocation takes the form:</p> invoking "<tt>bjam --help</tt>". The full invocation takes the form:</p>
<blockquote> <blockquote>
<p><code>bjam&nbsp;[<i>options</i>...] [install|stage]</code></p> <p><code>bjam&nbsp;[<i>options</i>...] [install|stage]</code></p>
@ -513,8 +596,9 @@
<td nowrap align="left" valign="top"><i>none</i></td> <td nowrap align="left" valign="top"><i>none</i></td>
<td align="left" valign="top">Only builds the Boost libraries. This <td align="left" valign="top">Only builds the Boost libraries. This
lets you do the first part of what the <tt>install</tt> action normally lets you do the first part of what the <tt>install</tt> action
does without copying the built libraries to the install location.</td> normally does without copying the built libraries to the install
location.</td>
</tr> </tr>
<tr> <tr>
@ -540,8 +624,8 @@
<tr> <tr>
<td nowrap align="left" valign="top"><tt>--help</tt></td> <td nowrap align="left" valign="top"><tt>--help</tt></td>
<td align="left" valign="top">Shows a short summary of the options and <td align="left" valign="top">Shows a short summary of the options
syntax of the command.</td> and syntax of the command.</td>
</tr> </tr>
<tr> <tr>
@ -590,8 +674,8 @@
<td nowrap align="left" valign="top"><tt>--builddir=DIR</tt></td> <td nowrap align="left" valign="top"><tt>--builddir=DIR</tt></td>
<td align="left" valign="top">Build in this location instead of <td align="left" valign="top">Build in this location instead of
building within the distribution tree. This moves where the sources for building within the distribution tree. This moves where the sources
the libraries are compiled to before they are installed. for the libraries are compiled to before they are installed.
Recommended!</td> Recommended!</td>
</tr> </tr>
@ -616,9 +700,9 @@
<tt>--with-python-root[=PYTHON_ROOT]</tt></td> <tt>--with-python-root[=PYTHON_ROOT]</tt></td>
<td align="left" valign="top">Build Boost.Python libraries with the <td align="left" valign="top">Build Boost.Python libraries with the
Python devel packages located at <tt>PYTHON_ROOT</tt>. The Boost.Python Python devel packages located at <tt>PYTHON_ROOT</tt>. The
libraries are built only if the build can find the Python development Boost.Python libraries are built only if the build can find the
package at this location.<br> Python development package at this location.<br>
Default; <tt>C:\tools\python</tt> on Win32.<br> Default; <tt>C:\tools\python</tt> on Win32.<br>
Default; <tt>/usr/local</tt> on Unix, Linux, etc.<br> Default; <tt>/usr/local</tt> on Unix, Linux, etc.<br>
Default; <tt>/usr</tt> on Cygwin.</td> Default; <tt>/usr</tt> on Cygwin.</td>
@ -634,19 +718,19 @@
</tr> </tr>
</table> </table>
<p>There are additional options as supported by <a href= <p>There are additional options as supported by <a href=
"../tools/build/v1/build_system.htm">Boost.Build</a> and <a href= "../tools/build/v1/build_system.htm">Boost.Build</a> and <a href=
"../tools/build/jam_src/index.html">Boost.Jam</a>. Of the additional options "../tools/build/jam_src/index.html">Boost.Jam</a>. Of the additional
perhaps the most imporant is "<tt>-s<a href= options perhaps the most imporant is "<tt>-s<a href=
"../tools/build/v1/build_system.htm#build">BUILD</a>=&lt;features/variants&gt;</tt>" "../tools/build/v1/build_system.htm#build">BUILD</a>=&lt;features/variants&gt;</tt>"
which lets you override what is built by default. The "<tt>&lt;features/variants&gt;</tt>" which lets you override what is built by default. The
value is a list, separated by spaces, of build requests. Features take the form "<tt>&lt;features/variants&gt;</tt>" value is a list, separated by
of a tag and a value or values. And variants are single symbolic names for a spaces, of build requests. Features take the form of a tag and a value or
collection of features. For example the default is to request "<tt>debug release values. And variants are single symbolic names for a collection of
&lt;runtime-link&gt;static/dynamic &lt;threading&gt;single/multi</tt>", in which features. For example the default is to request "<tt>debug release
"<tt>debug</tt>" and "<tt>release</tt>" are variants, and the rest features &lt;runtime-link&gt;static/dynamic &lt;threading&gt;single/multi</tt>",
with two values each.</p> in which "<tt>debug</tt>" and "<tt>release</tt>" are variants, and the
rest features with two values each.</p>
<p>If you have some feedback about the build and install process please <p>If you have some feedback about the build and install process please
drop us a line at the <a href="mailing_lists.htm#jamboost">Boost.Build drop us a line at the <a href="mailing_lists.htm#jamboost">Boost.Build
@ -656,12 +740,12 @@
<h2><a name="Results"></a>Results</h2> <h2><a name="Results"></a>Results</h2>
<p>The results of building come in to forms: static libraries, and dynamic <p>The results of building come in to forms: static libraries, and
libraries. Depending on the platform the libraries produced have different dynamic libraries. Depending on the platform the libraries produced have
names to accommodate the platform requirements. For a single Boost library different names to accommodate the platform requirements. For a single
the build with the default will produce eight different libraries. For Boost library the build with the default will produce eight different
example building the Boost.Datetime library on Unix type system it would libraries. For example building the Boost.Datetime library on Unix type
produce:</p> system it would produce:</p>
<ol> <ol>
<li><tt>libboost_date_time-gcc-d-1_31.so</tt></li> <li><tt>libboost_date_time-gcc-d-1_31.so</tt></li>
@ -678,14 +762,16 @@
<li><tt>libboost_date_time-gcc-1_31.a</tt></li> <li><tt>libboost_date_time-gcc-1_31.a</tt></li>
<li><tt>libboost_date_time-gcc-mt-1_31.a</tt><br></li> <li><tt>libboost_date_time-gcc-mt-1_31.a</tt><br>
</li>
</ol> </ol>
<table summary="" border="0" cellspacing="0" cellpadding="0" width="100%"> <table summary="" border="0" cellspacing="0" cellpadding="0" width=
"100%">
<tr> <tr>
<td colspan="11"> <td colspan="11">
<table summary="" border="0" cellspacing="2" cellpadding="2" bgcolor= <table summary="" border="0" cellspacing="2" cellpadding="2"
"#CCCCCC"> bgcolor="#CCCCCC">
<tr> <tr>
<th>&middot; Library Prefix</th> <th>&middot; Library Prefix</th>
</tr> </tr>
@ -713,8 +799,8 @@
"+1">boost_date_time</font></tt></td> "+1">boost_date_time</font></tt></td>
<td colspan="10"> <td colspan="10">
<table summary="" border="0" cellspacing="2" cellpadding="2" bgcolor= <table summary="" border="0" cellspacing="2" cellpadding="2"
"#CCCCCC"> bgcolor="#CCCCCC">
<tr> <tr>
<th>&middot; Toolset</th> <th>&middot; Toolset</th>
</tr> </tr>
@ -739,13 +825,15 @@
</tr> </tr>
<tr> <tr>
<td rowspan="4" valign="bottom"><tt><font size="+1">-</font></tt></td> <td rowspan="4" valign="bottom"><tt><font size=
"+1">-</font></tt></td>
<td rowspan="4" valign="bottom"><tt><font size="+1">mt</font></tt></td> <td rowspan="4" valign="bottom"><tt><font size=
"+1">mt</font></tt></td>
<td colspan="6"> <td colspan="6">
<table summary="" border="0" cellspacing="2" cellpadding="2" bgcolor= <table summary="" border="0" cellspacing="2" cellpadding="2"
"#CCCCCC"> bgcolor="#CCCCCC">
<tr> <tr>
<th>&middot; Runtime</th> <th>&middot; Runtime</th>
</tr> </tr>
@ -770,14 +858,15 @@
</tr> </tr>
<tr> <tr>
<td rowspan="2" valign="bottom"><tt><font size="+1">-</font></tt></td> <td rowspan="2" valign="bottom"><tt><font size=
"+1">-</font></tt></td>
<td rowspan="2" valign="bottom"><tt><font size= <td rowspan="2" valign="bottom"><tt><font size=
"+1">1_31</font></tt></td> "+1">1_31</font></tt></td>
<td colspan="2"> <td colspan="2">
<table summary="" border="0" cellspacing="2" cellpadding="2" bgcolor= <table summary="" border="0" cellspacing="2" cellpadding="2"
"#CCCCCC"> bgcolor="#CCCCCC">
<tr> <tr>
<th>&middot; Library Type</th> <th>&middot; Library Type</th>
</tr> </tr>
@ -798,8 +887,8 @@
<p>The "lib" prefix on the libraries is a requirement on many platforms, <p>The "lib" prefix on the libraries is a requirement on many platforms,
like Unix, and on others like GCC running on Windows. The prefix is like Unix, and on others like GCC running on Windows. The prefix is
therefore added to all libraries on Unix type systems, and to static therefore added to all libraries on Unix type systems, and to static
libraries on Windows. That is on Unix shared libraries and static libraries libraries on Windows. That is on Unix shared libraries and static
(object archives) are named respectively:</p> libraries (object archives) are named respectively:</p>
<ul> <ul>
<li><tt>lib*.so</tt></li> <li><tt>lib*.so</tt></li>
@ -807,8 +896,8 @@
<li><tt>lib*.a</tt></li> <li><tt>lib*.a</tt></li>
</ul> </ul>
<p>On Windows shared libraries do not have the prefix to differentiate the <p>On Windows shared libraries do not have the prefix to differentiate
import libraries from static libraries. Consequently on Windows the the import libraries from static libraries. Consequently on Windows the
libraries are named:</p> libraries are named:</p>
<ul> <ul>
@ -827,11 +916,11 @@
<h3>Toolset</h3> <h3>Toolset</h3>
<p>The toolset name is an abbreviation based on the compiler you are <p>The toolset name is an abbreviation based on the compiler you are
building with. The abbreviation is composed of a short, 2 to 4 characters, building with. The abbreviation is composed of a short, 2 to 4
tag for the compiler and a version number of the compiler's major and minor characters, tag for the compiler and a version number of the compiler's
revision (if available). For example if your toolset is major and minor revision (if available). For example if your toolset is
"<tt>gcc-3.2.3</tt>" the toolset tag would be "<tt>gcc32</tt>". The toolset "<tt>gcc-3.2.3</tt>" the toolset tag would be "<tt>gcc32</tt>". The
abbreviations used are as follows:</p> toolset abbreviations used are as follows:</p>
<table border="1" cellpadding="5" summary=""> <table border="1" cellpadding="5" summary="">
<tr> <tr>
@ -869,7 +958,8 @@
</tr> </tr>
<tr> <tr>
<td><code><a href="../tools/build/v1/cwpro9-tools.html">cwpro</a><a href="../tools/build/v1/cwpro8-tools.html">9</a></code></td> <td><code><a href="../tools/build/v1/cwpro9-tools.html">cwpro</a><a
href="../tools/build/v1/cwpro8-tools.html">9</a></code></td>
<td><tt><code>cw</code></tt><code>9</code></td> <td><tt><code>cw</code></tt><code>9</code></td>
</tr> </tr>
@ -1023,16 +1113,16 @@
<h3>Threading</h3> <h3>Threading</h3>
<p>This tag indicates if the library is compiled with threading support. If <p>This tag indicates if the library is compiled with threading support.
threading is enabled "<tt>-mt</tt>" is added, otherwise nothing is If threading is enabled "<tt>-mt</tt>" is added, otherwise nothing is
added.</p> added.</p>
<h3>Runtime</h3> <h3>Runtime</h3>
<p>This specifies the type of runtime the library was compiled against, and <p>This specifies the type of runtime the library was compiled against,
the type of code that is compiled. More commonly this encodes the ABI and the type of code that is compiled. More commonly this encodes the ABI
variation used in the code. For each feature of the runtime system and code variation used in the code. For each feature of the runtime system and
compilation option a single letter is added to this tag.</p> code compilation option a single letter is added to this tag.</p>
<table border="1" cellpadding="5" summary=""> <table border="1" cellpadding="5" summary="">
<tr> <tr>
@ -1087,19 +1177,19 @@
<p>This is the short label for the version of the Boost Libraries. The <p>This is the short label for the version of the Boost Libraries. The
major and minor version numbers are taken together separated by an major and minor version numbers are taken together separated by an
underscore. For example version 1.31.0 would be tagged as "<tt>-1_31</tt>". underscore. For example version 1.31.0 would be tagged as
The patch version number is not included because it is assumed that patch "<tt>-1_31</tt>". The patch version number is not included because it is
versions are upward compatible.</p> assumed that patch versions are upward compatible.</p>
<h3>Library Type</h3> <h3>Library Type</h3>
<p>The extension holds the type of library. This follows the platform <p>The extension holds the type of library. This follows the platform
requirements. On Windows this is "<tt>.dll</tt>" for shared libraries, and requirements. On Windows this is "<tt>.dll</tt>" for shared libraries,
"<tt>.lib</tt>" for static libraries including import libraries. On Unix and "<tt>.lib</tt>" for static libraries including import libraries. On
this is ".a" for static libraries (archives), and ".so" for shared Unix this is ".a" for static libraries (archives), and ".so" for shared
libraries. For toolsets that support it in Unix they will also have a full libraries. For toolsets that support it in Unix they will also have a
version extension (for example "<tt>.so.1.31.0</tt>") with a symbolic link full version extension (for example "<tt>.so.1.31.0</tt>") with a
for the un-versioned library.</p> symbolic link for the un-versioned library.</p>
<h2><a name="Additional_Steps"></a>Additional Steps</h2> <h2><a name="Additional_Steps"></a>Additional Steps</h2>
@ -1108,20 +1198,23 @@
<ul> <ul>
<li><a href="../libs/config/config.htm#configuring">Configure the boost <li><a href="../libs/config/config.htm#configuring">Configure the boost
source code</a>. This step should not be required on the vast majority of source code</a>. This step should not be required on the vast majority
platforms, but if you're trying to build Boost on an untested or of platforms, but if you're trying to build Boost on an untested or
unsupported platform it may be necessary.<br> unsupported platform it may be necessary.<br>
<br></li> <br>
</li>
<li>If Boost.Build has problems detecting your Python installation it <li>If Boost.Build has problems detecting your Python installation it
will print a short messages about how to configure for finding the Python will print a short messages about how to configure for finding the
installation. For more information, see these detailed <a href= Python installation. For more information, see these detailed <a href=
"../libs/python/doc/building.html#building">instructions</a>.</li> "../libs/python/doc/building.html#building">instructions</a>.</li>
</ul> </ul>
<hr> <hr>
<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" <p>Revised <!--webbot bot="Timestamp" s-type="EDITED"
s-format="%d %B, %Y" startspan -->07 January, 2004<!--webbot bot="Timestamp" endspan i-checksum="38706" --></p> s-format="%d %B, %Y" startspan -->07
January, 2004
<!--webbot bot="Timestamp" endspan i-checksum="38706" --></p>
<p>Copyright &copy; Rene Rivera 2003.<br> <p>Copyright &copy; Rene Rivera 2003.<br>
Copyright &copy; Jens Maurer 2001.</p> Copyright &copy; Jens Maurer 2001.</p>
@ -1132,3 +1225,4 @@
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p> "http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body> </body>
</html> </html>