boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-15 00:52:16 +00:00
Code Issues Projects Releases Wiki Activity

Clneaup... Update license statements and HTMLTidy.

Browse Source 
[SVN r25538]
This commit is contained in:
Rene Rivera
2004-10-03 16:27:43 +00:00
parent 82120cb6cf
commit bb4d03e57e
32 changed files with 537 additions and 447 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
v1/acc-tools.jam
View File

@@ -1,9 +1,6 @@
# (C) Copyright Toon Knapen 2002, David Abrahams 2002
# Permission to copy, use,
# modify, sell and distribute this software is granted provided this
# copyright notice appears in all copies. This software is provided
# "as is" without express or implied warranty, and with no claim as
# to its suitability for any purpose.
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
#
# Jam tools information for :

6
v1/borland-tools.html
View File

@@ -74,9 +74,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

193
v1/build_system.htm
View File

@@ -29,7 +29,7 @@
</tbody>
</table>
<h2><a name="synopsis">Synopsis</a></h2>
<h2><a name="synopsis" id="synopsis">Synopsis</a></h2>
<p>Boost.Build is a system for large project software construction built on
<a href="../jam_src/index.html">Boost.Jam</a>, a descendant of "<a href=
@@ -57,13 +57,13 @@
<li>Automatic building of subproject dependencies</li>
</ul>
<h2><a name="status">Status</a></h2>Boost.Build v1 is a useful, mature
system. However, its design and structure are not easily adapted to support
some of the features we'd like to see in the future. To this end, the
Boost.Build developers are working on <a href=
"../v2/boost_build_v2.html">Boost.Build v2</a>, which is pretty usable
already. If you are interested in contributing to this effort or you wish
to discuss the design of Boost.Build, please post inquiries to the <a href=
<h2><a name="status" id="status">Status</a></h2>Boost.Build v1 is a useful,
mature system. However, its design and structure are not easily adapted to
support some of the features we'd like to see in the future. To this end,
the Boost.Build developers are working on <a href=
"../v2/index.html">Boost.Build v2</a>, which is pretty usable already. If
you are interested in contributing to this effort or you wish to discuss
the design of Boost.Build, please post inquiries to the <a href=
"http://groups.yahoo.com/group/jamboost/">jamboost</a> mailing list at
yahoogroups.
@@ -186,14 +186,14 @@
<li><a href="#footnotes">Footnotes</a></li>
</ul>
<h2><a name="getting_started">Getting Started</a></h2>
<h2><a name="getting_started" id="getting_started">Getting Started</a></h2>
<h3><a name="installing_jam">Installing Boost.Jam</a></h3>Follow these
<a href="../../../more/getting_started.html#step2">instructions</a> to
acquire a bjam executable for your platform. Install it somewhere in your
path.
<h3><a name="installing_jam" id="installing_jam">Installing
Boost.Jam</a></h3>Follow these <a href=
"../../../more/getting_started.html#step2">instructions</a> to acquire a
bjam executable for your platform. Install it somewhere in your path.
<h3><a name="initiating">Initiating a Build</a></h3>
<h3><a name="initiating" id="initiating">Initiating a Build</a></h3>
<p>Boost.Build responds to several global variable settings. The easiest
way to get going is usually to use environment variables, though you can
@@ -296,7 +296,8 @@ bjam "-sBUILD=debug release"
</tr>
</table>
<h3><a name="setting_variables">Setting Jam Variables</a></h3>
<h3><a name="setting_variables" id="setting_variables">Setting Jam
Variables</a></h3>
<p>The "<tt>-s</tt>" options in the command lines above are passing
variable settings to the build system. There are actually three ways to do
@@ -324,11 +325,11 @@ bjam "-sBUILD=debug release"
file is a convenient place to make global settings.</li>
</ul>
<h3><a name="example_jamfile">An Example Jamfile</a></h3>Here is an example
of a simple subproject Jamfile. In this example, it is assumed that the
user has set <tt>BOOST_ROOT</tt>, either as an environment variable, on the
command-line or in the project's <tt><a href="#jamrules">Jamrules</a></tt>
file:
<h3><a name="example_jamfile" id="example_jamfile">An Example
Jamfile</a></h3>Here is an example of a simple subproject Jamfile. In this
example, it is assumed that the user has set <tt>BOOST_ROOT</tt>, either as
an environment variable, on the command-line or in the project's
<tt><a href="#jamrules">Jamrules</a></tt> file:
<blockquote>
<pre>
@@ -362,7 +363,7 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
</pre>
</blockquote>
<h3><a name="support_files">Support Files</a></h3>
<h3><a name="support_files" id="support_files">Support Files</a></h3>
<p>To use the build system, the following must be located in your project's
root directory, or in a directory specified in the
@@ -404,20 +405,21 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
</table>The <tt>boost-base.jam</tt> file is temporary, and will eventually
be compiled into our Jam executable.
<h2><a name="design">Basic Design and Terminology</a></h2>This section
gives an overview of the way that the system works, outlining the system's
capabilities and overall design. It also introduces the terminology and
concepts necessary to understand the sections on writing Jamfiles and
command-line invocations.
<h2><a name="design" id="design">Basic Design and Terminology</a></h2>This
section gives an overview of the way that the system works, outlining the
system's capabilities and overall design. It also introduces the
terminology and concepts necessary to understand the sections on writing
Jamfiles and command-line invocations.
<h3><a name="project_subproject">Projects and Subprojects</a></h3>
<h3><a name="project_subproject" id="project_subproject">Projects and
Subprojects</a></h3>
<p>A <b>project</b> is a source directory tree containing at least one
<tt>Jamfile</tt>. The root directory of the project is known as the
<b>project root</b>. <a name="jamrules">The</a> root directory of a project
may contain a <tt>Jamrules</tt> file, which contains project-specific Jam
code. If the <tt>Jamrules</tt> file is not present when Jam is invoked, a
warning will be issued.</p>
<b>project root</b>. <a name="jamrules" id="jamrules">The</a> root
directory of a project may contain a <tt>Jamrules</tt> file, which contains
project-specific Jam code. If the <tt>Jamrules</tt> file is not present
when Jam is invoked, a warning will be issued.</p>
<p>Subdirectories containing <tt>Jamfile</tt>s are called <b>subproject
directories</b>. Each such <tt>Jamfile</tt> describes a
@@ -426,15 +428,14 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
<p>The <b>build system installation directory</b> is a directory containing
Jam files describing compilers and build variants. The installation
directory can be specified in a file called <tt>boost-build.jam</tt> in the
project root directory. This file should contain a line
<tt>boost-build $path-to-installation-dir</tt>. If no such file is
available the environment variable
<tt>BOOST_BUILD_PATH</tt> will be used. This lists a set of directories to search for
the files comprising the build system. If the installation directory is not
specified, it is the same as the project root, and
<tt>BOOST_BUILD_PATH</tt> is set to include that directory.</p>
project root directory. This file should contain a line <tt>boost-build
$path-to-installation-dir</tt>. If no such file is available the
environment variable <tt>BOOST_BUILD_PATH</tt> will be used. This lists a
set of directories to search for the files comprising the build system. If
the installation directory is not specified, it is the same as the project
root, and <tt>BOOST_BUILD_PATH</tt> is set to include that directory.</p>
<h3><a name="targets">Targets</a></h3>
<h3><a name="targets" id="targets">Targets</a></h3>
<p>Each <tt>Jamfile</tt> describes one or more <b>main targets</b>.</p>
@@ -453,7 +454,7 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
directory can be customized by changing the <tt>BIN_DIRECTORY</tt>
variable.</li>
<li><a name="all_locate_target">If the variable
<li><a name="all_locate_target" id="all_locate_target">If the variable
<tt>ALL_LOCATE_TARGET</tt> is set</a>, it specifies an alternate build
directory tree whose structure mirrors that of the project. In this case,
built targets of a subproject are generated into the corresponding
@@ -462,7 +463,7 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
directory tree known as the target's <b>build root</b>, where all
intermediate and final targets resulting from that main target are located.
<h3><a name="features">Features and Properties</a></h3>
<h3><a name="features" id="features">Features and Properties</a></h3>
<p>A <b>feature</b> is a normalized (toolset-independent) description of an
individual build parameter, such as whether inlining is enabled. Each
@@ -503,7 +504,7 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
<b>property</b>. The prefixes <i>simple</i>, <i>free</i>, <i>path</i>, and
<i>dependency</i> apply to properties in an analogous way to features.</p>
<h3><a name="variants">Build Variants</a></h3>
<h3><a name="variants" id="variants">Build Variants</a></h3>
<p>A build variant, or simply <b>variant</b> is a named set of build
properties describing how targets should be built. Typically you'll want at
@@ -541,7 +542,7 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
so <tt>debug</tt> may mean a slightly different set of properties for two
different compilers.</p>
<h3><a name="subvariants">Subvariants</a></h3>
<h3><a name="subvariants" id="subvariants">Subvariants</a></h3>
<p>When a target is built with <i>simple</i> properties that don't exactly
match those specified in a build variant, the non-matching features are
@@ -621,7 +622,7 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
base variant or subvariant, is known as a <b>build configuration</b>, or
simply a <b>build</b>.</p>
<h3><a name="dependents">Dependent Targets</a></h3>
<h3><a name="dependents" id="dependents">Dependent Targets</a></h3>
<p>When a main target depends on the product of a second main target (as
when an executable depends on and links to a static library), each build
@@ -635,19 +636,19 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
compilation units. This danger can be minimized by encapsulating such
feature differences inside of build variants.</p>
<h2><a name="usage">Usage</a></h2>
<h2><a name="usage" id="usage">Usage</a></h2>
<p>This section describes how to start a build from the command-line and
how to write project and subproject Jamfiles. It also describes the other
files written in the Jam language: build-tool specification files, feature
descriptions files.</p>
<h3><a name="command_line">The Command Line</a></h3>
<h3><a name="command_line" id="command_line">The Command Line</a></h3>
<p>This section describes in detail how the build system can be
invoked.</p>
<h4><a name="user_targets">User Targets</a></h4>
<h4><a name="user_targets" id="user_targets">User Targets</a></h4>
<p>The Jam command line ends with an optional list of target names; if no
target names are supplied, the built-in pseudotarget <tt>all</tt> is built.
@@ -676,7 +677,7 @@ exe my_target : my_source1.cpp my_source2.c ;
Please see <a href="#target_names">this section</a> for a more complete
description of how to name particular targets in a build.</p>
<h4><a name="user_globals">Global Variables</a></h4>
<h4><a name="user_globals" id="user_globals">Global Variables</a></h4>
<p>This is a partial list of global variables that can be set on the
command-line. Of course you are free to write your own Jam rules which
@@ -697,7 +698,7 @@ exe my_target : my_source1.cpp my_source2.c ;
</tr>
<tr>
<td rowspan="2"><tt><a name="tools">TOOLS</a></tt>
<td rowspan="2"><tt><a name="tools" id="tools">TOOLS</a></tt>
<!-- <td rowspan="2">Toolsets to build with --></td>
<td rowspan="2">Platform-dependent</td>
@@ -714,7 +715,7 @@ exe my_target : my_source1.cpp my_source2.c ;
</tr>
<tr>
<td rowspan="4"><tt><a name="build">BUILD</a></tt>
<td rowspan="4"><tt><a name="build" id="build">BUILD</a></tt>
<!-- <td rowspan="4">Build configuration (see -->
<!-- <a href="#default_build">here</a>). --></td>
@@ -760,9 +761,11 @@ exe my_target : my_source1.cpp my_source2.c ;
</tr>
</table>This section describes how to write a Jamfile for a subproject.
<h3><a name="subproject_jamfiles">SubProject Jamfiles</a></h3>
<h3><a name="subproject_jamfiles" id="subproject_jamfiles">SubProject
Jamfiles</a></h3>
<h4><a name="subproject_rule">The <tt>subproject</tt> rule</a></h4>
<h4><a name="subproject_rule" id="subproject_rule">The <tt>subproject</tt>
rule</a></h4>
<p>A subproject's Jamfile begins with an invocation of the
<tt>subproject</tt> rule that specifies the subproject's location relative
@@ -785,7 +788,8 @@ project-root ;
</pre>
</blockquote>
<h4><a name="main_targets">Describing Main Targets</a></h4>
<h4><a name="main_targets" id="main_targets">Describing Main
Targets</a></h4>
<p>A main target is described using the following syntax:</p>
@@ -821,8 +825,8 @@ project-root ;
<li>
<i>sources</i> is a list of paths to source files and dependency
targets. <a name="dependency">The</a> syntax for dependency targets is
described by the following grammar:
targets. <a name="dependency" id="dependency">The</a> syntax for
dependency targets is described by the following grammar:
<blockquote>
<pre>
@@ -859,9 +863,10 @@ project-root ;
</li>
<li>
<i><a name="target_requirements">requirements</a></i> specifies the
build properties intrinsic to the target. Requirements are given as
sets of optionally-<b>qualified build properties</b>:
<i><a name="target_requirements" id=
"target_requirements">requirements</a></i> specifies the build
properties intrinsic to the target. Requirements are given as sets of
optionally-<b>qualified build properties</b>:
<blockquote>
<pre>
@@ -879,8 +884,8 @@ project-root ;
</li>
<li>
<i><a name="default_build">default-BUILD</a></i> specifies the
configurations that should be built if the <tt><a href=
<i><a name="default_build" id="default_build">default-BUILD</a></i>
specifies the configurations that should be built if the <tt><a href=
"#build">BUILD</a></tt> variable is not otherwise specified. Any
elements not beginning with ``<tt>&lt;</tt>...<tt>&gt;</tt>'' refer to
build variants. Other elements use the same syntax as the <a href=
@@ -919,7 +924,8 @@ exe test : test.cpp &lt;lib&gt;basic ;
"#default_build">default-BUILD</a></i>, more-specific qualification
overrides less-specific.</p>
<h4><a name="template_targets">Describing Template Targets</a></h4>
<h4><a name="template_targets" id="template_targets">Describing Template
Targets</a></h4>
<p>Template targets provide a way to handle commonalities between projects
targets. They have the same form as <a href="#main_targets">main
@@ -933,7 +939,8 @@ exe test : test.cpp &lt;lib&gt;basic ;
defines, include paths and additional compiler flags common to all targets
in the project.</p>
<h4><a name="stage_targets">Describing Stage Targets</a></h4>
<h4><a name="stage_targets" id="stage_targets">Describing Stage
Targets</a></h4>
<p>Stage targets are a special kind of target that don't build a single
file but to a collection of files. The goal is to create a directory which
@@ -983,7 +990,7 @@ exe test : test.cpp &lt;lib&gt;basic ;
target.<br></li>
</ul>
<h4><a name="jamfile_example">Example</a></h4>
<h4><a name="jamfile_example" id="jamfile_example">Example</a></h4>
<p>This artificially complex example shows how two executables called "foo"
and "fop" might be described in a Jamfile. All common settings are factored
@@ -1056,13 +1063,13 @@ exe fop : &lt;template&gt;executable fop.cpp ;
and dynamically-linked subvariants of the debug variant.</li>
</ul>
<h3><a name="external_project">Using External Projects</a></h3>To use
dependencies such as libraries from another project tree, first use the
<code>project</code> rule to declare a project id and location for the
external project. Then add the appropriate external <a href=
"#dependency">dependency target specification</a> to your program's list of
sources. For example, if you are developing a program which uses the
Boost.Threads library, you might write
<h3><a name="external_project" id="external_project">Using External
Projects</a></h3>To use dependencies such as libraries from another project
tree, first use the <code>project</code> rule to declare a project id and
location for the external project. Then add the appropriate external
<a href="#dependency">dependency target specification</a> to your program's
list of sources. For example, if you are developing a program which uses
the Boost.Threads library, you might write
<blockquote>
<pre>
@@ -1076,7 +1083,8 @@ project boost : /home/dave/boost-cvs ;
</pre>
</blockquote>in your target's list of sources.
<h3><a name="requirement_rules">Requirement Rules</a></h3>
<h3><a name="requirement_rules" id="requirement_rules">Requirement
Rules</a></h3>
<p>Target requirements support the use of auxiliary rules to allow for more
complex decisions about the requirements. If specified, by using the name
@@ -1144,7 +1152,8 @@ project boost : /home/dave/boost-cvs ;
</table>
</blockquote>
<h3><a name="install_descriptions">Install Descriptions</a></h3>
<h3><a name="install_descriptions" id="install_descriptions">Install
Descriptions</a></h3>
<p>Installable files and targets are described with:</p>
@@ -1201,7 +1210,8 @@ install <i>name</i> <i>type</i> : <i>sources</i>... : [<i>options</i>]... ;
<br></li>
</ul>
<h3><a name="feature_description">Feature Descriptions</a></h3>
<h3><a name="feature_description" id="feature_description">Feature
Descriptions</a></h3>
<p>Features are described by stating the feature type (simple features are
specified with "<tt>feature</tt>"), followed by the feature name. An
@@ -1209,7 +1219,8 @@ install <i>name</i> <i>type</i> : <i>sources</i>... : [<i>options</i>]... ;
feature. Examples can be found in <a href=
"features.jam">features.jam</a>.</p>
<h3><a name="variant_description">Variant Descriptions</a></h3>
<h3><a name="variant_description" id="variant_description">Variant
Descriptions</a></h3>
<p>Variants are described with the following syntax:</p>
@@ -1238,7 +1249,8 @@ variant my-release : my-globals release ;
</blockquote>More examples can be found in <a href=
"features.jam">features.jam</a>.
<h3><a name="toolset_description">Toolset Description Files</a></h3>
<h3><a name="toolset_description" id="toolset_description">Toolset
Description Files</a></h3>
<p>Toolset descriptions are located in the project's root directory, or a
directory specified by <tt>BOOST_BUILD_INSTALLATION</tt>, which may be set
@@ -1340,7 +1352,7 @@ flags <i>toolset variable condition</i> [: <i>value</i>...]
</li>
</ol>
<h4><a name="toolset_example">Example</a></h4>
<h4><a name="toolset_example" id="toolset_example">Example</a></h4>
<p>The description of the <tt>flags</tt> rule above is actually more
complicated than it sounds. For example, the following line might be used
@@ -1374,9 +1386,9 @@ flags msvc HDRS &lt;include&gt; ;
<p>The use of these variables should be apparent from the declaration of
<tt>actions msvc-C++-action</tt> in the previous section.</p>
<h2><a name="internals">Internals</a></h2>
<h2><a name="internals" id="internals">Internals</a></h2>
<h3><a name="target_names">Target Names</a></h3>
<h3><a name="target_names" id="target_names">Target Names</a></h3>
<p>In addition to <a href="#user_targets">user targets</a>, which
correspond directly to the names the user writes in her subproject Jamfile,
@@ -1404,7 +1416,8 @@ flags msvc HDRS &lt;include&gt; ;
targets will be identified this way.</li>
</ul>
<h3><a name="internal_globals">Global Variables</a></h3>
<h3><a name="internal_globals" id="internal_globals">Global
Variables</a></h3>
<p>This section describes some of the global variables used by the build
system. Please note that some parts of the system (particularly those in
@@ -1461,9 +1474,9 @@ flags msvc HDRS &lt;include&gt; ;
<tt><i>subproject!id</i>/target/toolset/variant/<i>subvariant-path</i></tt>.</li>
</ul>
<h2><a name="design_criteria">Design Criteria</a></h2>
<h2><a name="design_criteria" id="design_criteria">Design Criteria</a></h2>
<h3><a name="assumptions">Assumptions</a></h3>
<h3><a name="assumptions" id="assumptions">Assumptions</a></h3>
<p>The requirements are driven by several basic assumptions:</p>
@@ -1476,7 +1489,7 @@ flags msvc HDRS &lt;include&gt; ;
compilers that almost no other assumptions can be made.</li>
</ul>
<h3><a name="requirements">Requirements</a></h3>
<h3><a name="requirements" id="requirements">Requirements</a></h3>
<p>This build system was designed to satisfy the following
requirements:</p>
@@ -1525,16 +1538,16 @@ flags msvc HDRS &lt;include&gt; ;
the source directories (they may be read-only)</li>
</ul>
<h2><a name="footnotes">Footnotes</a></h2><a name="1">[1]</a> Boost Jam is
actually descended directly from <a href=
<h2><a name="footnotes" id="footnotes">Footnotes</a></h2><a name="1" id=
"1">[1]</a> Boost Jam is actually descended directly from <a href=
"http://freetype.sourceforge.net/jam/index.html">FTJam</a>, which was
itself a variant of <a href=
"http://www.perforce.com/jam/jam.html">Jam/MR</a>. It is hoped that crucial
features we rely on will eventually be incorporated back into the Jam/MR
release.
<p><a name="2">[2]</a> Note: right now, a dependency feature of a main
target makes <b>all</b> resulting built targets dependent, including
<p><a name="2" id="2">[2]</a> Note: right now, a dependency feature of a
main target makes <b>all</b> resulting built targets dependent, including
intermediate targets. That means that if an executable is dependent on an
external library, and that library changes, all the sources comprising the
executable will be recompiled as well. This behavior should probably be
@@ -1544,14 +1557,14 @@ flags msvc HDRS &lt;include&gt; ;
<p>Revised
<!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan
-->8 September, 2003
<!--webbot bot="Timestamp" endspan i-checksum="13972"
<!--webbot bot="Timestamp" endspan i-checksum="13972"
--></p>
<p>Copyright &copy; Dave Abrahams 2001.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

22
v1/como-tools.html
View File

@@ -33,12 +33,12 @@
<p>Boost.Build's como and como-win32 toolsets support the <a href=
"http://www.comeaucomputing.com">Comeau Computing</a> C/C++ Compiler.</p>
<h2>Configuration Variables</h2><p>The como and como-win32 toolsets respond to
the following variables which can be set in the environment or configured
on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:
</p>
<h2>Configuration Variables</h2>
<p>The como and como-win32 toolsets respond to the following variables
which can be set in the environment or configured on the jam command-line
using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:</p>
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
@@ -104,7 +104,8 @@
<tr>
<td><code>COMO_BACKEND</code></td>
<td>Backend abbreviation, e.g. <code>vc7</code>, <code>bcc</code>, <code>dig</code>, etc.</td>
<td>Backend abbreviation, e.g. <code>vc7</code>, <code>bcc</code>,
<code>dig</code>, etc.</td>
<td><code>vc7</code></td>
@@ -120,7 +121,6 @@
<td><code>como-win32</code> toolset only.</td>
</tr>
</table>
<hr>
@@ -131,9 +131,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

90
v1/cw-tools.html
View File

@@ -22,8 +22,7 @@
<td valign="top">
<h1 align="center">Boost.Build</h1>
<h2 align="center">cw toolset</h2>
<h2 align="center">cw toolset</h2>
</td>
</tr>
</table>
@@ -31,52 +30,59 @@
<h2>Introduction</h2>
<p>Boost.Build's cw toolset supports the <a href=
"http://www.metrowerks.com">Metrowerks CodeWarrior</a> Pro 6.x, 7.x, 8.x and
9.x tools. This toolsets handles allteh variations for the CodeWarrior command
line compiler tools.</p>
<p>Boost.Build's cw toolset supports the <a href=
"http://www.metrowerks.com">Metrowerks CodeWarrior</a> Pro 6.x, 7.x, 8.x
and 9.x tools. This toolsets handles allteh variations for the CodeWarrior
command line compiler tools.</p>
<h2>Configuration Variables</h2>
The cw toolset responds to the following variables which can be set in the environment
or configured on the jam command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>CW_ROOT</code></td>
<td>Path to installation of Metrowerks Codewarrior.</td>
<td><i>empty</i></td>
<td rowspan="2">The toolset attempts to figure out what the version and root
of the tools are by looking at the environment and at the registry (on Windows).
If nothing is given the newest available toolset is used.</td>
</tr>
<tr>
<td><code>CW_VERSION</code></td>
<td>Version to use. Valid values are: 6.0, 7.0, 8.0, 9.0.</td>
<td><i>empty</i></td>
</tr>
</table>
<h2>Configuration Variables</h2>The cw toolset responds to the following
variables which can be set in the environment or configured on the jam
command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
<th>Semantics</th>
<th>Default</th>
<th>Notes</th>
</tr>
<tr>
<td><code>CW_ROOT</code></td>
<td>Path to installation of Metrowerks Codewarrior.</td>
<td><i>empty</i></td>
<td rowspan="2">The toolset attempts to figure out what the version and
root of the tools are by looking at the environment and at the registry
(on Windows). If nothing is given the newest available toolset is
used.</td>
</tr>
<tr>
<td><code>CW_VERSION</code></td>
<td>Version to use. Valid values are: 6.0, 7.0, 8.0, 9.0.</td>
<td><i>empty</i></td>
</tr>
</table>
<hr>
<p>Revised
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
23 February, 2004
<!--webbot bot="Timestamp" endspan i-checksum="39359" -->
</p>
23 February, 2004
<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Copyright Rene Rivera 2004.</p>
<p>Copyright Rene Rivera 2004.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See accompanying
file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

16
v1/darwin-tools.html
View File

@@ -36,12 +36,12 @@
tailored to account for the various "features" that Apple implemented to
work in the Darwin OS Mach kernel.</p>
<h2><a name="configuration">Configuration Variables</a></h2>Because of the
already specific nature of this toolset there are no additional
configuration variables.
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>Because of the already specific nature of this toolset
there are no additional configuration variables.
<h2><a name="features">Toolset-Specific Features</a></h2>The following
<code>darwin</code>-specific <a href=
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>The
following <code>darwin</code>-specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:
@@ -89,9 +89,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

52
v1/dmc-stlport-tools.html
View File

@@ -32,24 +32,24 @@
<h2>Introduction</h2>
<p>Boost.Build's <a href="dmc-stlport-tools.jam">dmc-stlport</a>
toolset supports the <a href="http://www.digitalmars.com/">Digital Mars C++</a>
<p>Boost.Build's <a href="dmc-stlport-tools.jam">dmc-stlport</a> toolset
supports the <a href="http://www.digitalmars.com/">Digital Mars C++</a>
command-line tools, using the <a href="http://www.stlport.org">STLport</a>
standard library implementation. It is designed to
allow you to build and test with multiple installed versions of STLPort, so
that objects build in each configuration will be built into separate
directories.</p>
standard library implementation. It is designed to allow you to build and
test with multiple installed versions of STLPort, so that objects build in
each configuration will be built into separate directories.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>
<p>The <code>dmc-stlport</code> toolset responds to the following
variables, which can be set in the environment or configured on the jam
command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is
an extension of the <a href="dmc-tools.html">dmc toolset</a> and therefore
responds to all of the Digital Mars <a href=
"dmc-tools.html#configuration">configuration variables</a> in addition to
those listed below.</p>
<h2><a name="configuration">Configuration Variables</a></h2>
<p>The
<code>dmc-stlport</code> toolset responds to the following variables, which can be
set in the environment or configured on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is an extension of the
<a href="dmc-tools.html">dmc toolset</a> and therefore responds to all of
the Digital Mars <a href="dmc-tools.html#configuration">configuration
variables</a> in addition to those listed below.
</p>
<p>In the table below, <i>version</i> corresponds to an STLPort version
number, e.g. "<code>4.5.3</code>".</p>
@@ -113,14 +113,13 @@
</tr>
</table>
<h2><a name="features">Toolset-Specific Features</a></h2>
<p>The following
<code>dmc-stlport</code>-specific <a href=
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>
<p>The following <code>dmc-stlport</code>-specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:
</p>
"build_system.htm#initiating"><code>BUILD</code></a> variable:</p>
<table border="1" summary="features">
<tr>
<th>Feature</th>
@@ -170,13 +169,14 @@
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
31 July, 2004 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
31 July, 2004
<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Copyright &copy; Dave Abrahams 2002, Aleksey Gurtovoy 2004.</p>
<p><small>Distributed under the Boost Software License, Version 1.0.
(See accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

31
v1/dmc-tools.html
View File

@@ -30,16 +30,17 @@
<h2>Introduction</h2>
<p>Boost.Build's <a href="dmc-tools.jam">dmc</a> toolset supports the
<a href="http://www.digitalmars.com/">Digital Mars C++</a> command-line tools.</p>
<p>Boost.Build's <a href="dmc-tools.jam">dmc</a> toolset supports the
<a href="http://www.digitalmars.com/">Digital Mars C++</a> command-line
tools.</p>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>
<p>The <code>dmc</code> toolset responds to the following variables, which
can be set in the environment or configured on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:</p>
<h2><a name="configuration">Configuration Variables</a></h2>
<p>The
<code>dmc</code> toolset responds to the following variables, which can be
set in the environment or configured on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:
</p>
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
@@ -56,23 +57,23 @@
<td>The path to the Digital Mars C++ installation directory</td>
<td>
<i>empty</i></td>
<td><i>empty</i></td>
<td>For example, <code>C:\Program Files\Digital Mars</code></td>
</tr>
</table>
<hr>
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
31 July, 2004 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
31 July, 2004
<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Copyright &copy; Dave Abrahams 2002, Aleksey Gurtovoy 2004.</p>
<p><small>Distributed under the Boost Software License, Version 1.0.
(See accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

5
v1/edg-tools.html
View File

@@ -68,5 +68,10 @@
<p><i>Written by <a href="../../../people/jens_maurer.htm">Jens
Maurer</a>.</i></p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

5
v1/gcc-nocygwin-tools.html
View File

@@ -43,7 +43,8 @@
using Cygwin, this toolset could save you having to install an additional
compiler.</p>
<h2><a name="configuration">Configuration Variables</a></h2>
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>
<p>This toolset operates in one of two modes - the default mode (which is
recommended) just extends the gcc toolset <a href=
@@ -122,7 +123,7 @@
standard library and build it with the -mno-cygwin option. Some details are
provided in the next section.</p>
<h2><a name="stlport">STLport iostream support</a></h2>
<h2><a name="stlport" id="stlport">STLport iostream support</a></h2>
<p>Here's the procedure for using the STLport iostream libraries with
gcc-nocygwin:</p>

18
v1/gcc-stlport-tools.html
View File

@@ -35,12 +35,12 @@
"http://www.stlport.org">STLport</a> as a replacement to the GNU
libg++.</p>
<h2><a name="configuration">Configuration Variables</a></h2>The gcc-stlport
toolset responds to the following variables which can be set in the
environment or configured on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. This toolset is an
extension to the <a href="gcc-tools.html">gcc toolset</a> and therefore
responds to all of the GCC <a href=
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The gcc-stlport toolset responds to the following
variables which can be set in the environment or configured on the jam
command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. This
toolset is an extension to the <a href="gcc-tools.html">gcc toolset</a> and
therefore responds to all of the GCC <a href=
"gcc-tools.html#configuration">configuration variables</a> in addition to
those listed below.
@@ -95,9 +95,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

8
v1/gcc-stlport-tools.jam
View File

@@ -1,8 +1,6 @@
# (C) Copyright David Abrahams and Carlos Pinto Coelho 2001. Permission
# to copy, use, modify, sell and distribute this software is granted
# provided this copyright notice appears in all copies. This software is
# provided "as is" without express or implied warranty, and with no
# claim as to its suitability for any purpose.
# (C) Copyright David Abrahams and Carlos Pinto Coelho 2001.
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
# this is simply an extension to the gcc toolset.
extends-toolset gcc ;

14
v1/gcc-tools.html
View File

@@ -37,10 +37,10 @@
"http://www.mingw.org">MinGW</a> has <a href="mingw-tools.html">its own
distinct toolset</a>.</p>
<h2><a name="configuration">Configuration Variables</a></h2>The gcc toolset
responds to the following variables, which can be set in the environment or
configured on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The gcc toolset responds to the following variables,
which can be set in the environment or configured on the jam command-line
using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:
<table border="1" summary="settings">
<tr>
@@ -124,9 +124,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

18
v1/index.html
View File

@@ -1,9 +1,21 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<meta http-equiv="refresh" content="0; URL=build_system.htm">
<meta http-equiv="refresh" content="0; URL=build_system.htm">
<title></title>
</head>
<body>
Automatic redirection failed, please go to
<a href="build_system.htm">build_system.htm</a>.
Automatic redirection failed, please go to <a href=
"build_system.htm">build_system.htm</a>.
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

180
v1/intel-linux-tools.html
View File

@@ -1,76 +1,110 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Boost.Build - intel-linux toolset</title>
<meta name="generator" content="HTML Tidy for Linux/x86 (vers 1st September 2003), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
</head>
<body link="#0000ff" vlink="#800080">
<table border="0" cellpadding="7" cellspacing="0" width="100%" summary="header">
<tr>
<td valign="top" width="300">
<h3><a href="http://www.boost.org"><img height="86" width="277" alt="C++ Boost" src="../../../c++boost.gif" border="0"></a></h3>
</td>
<td valign="top">
<h1 align="center">Boost.Build</h1>
<h2 align="center">intel-linux toolset</h2>
</td>
</tr>
</table>
<hr>
<h2>Introduction</h2>
<p>Boost.Build's intel-linux toolset supports the <a href="http://www.intel.com/software/products/compilers/clin/index.htm">
Intel C++ Compiler for Linux</a>.</p>
<h2>Configuration Variables</h2>
<P>
The intel-linux toolset responds to the following variables which can be set in
the environment or configured on the jam command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>.
If neither variable is set but <code>iccvars.sh</code> can be found in the <code>PATH</code>,
then the version of the tools installed where <code>iccvars.sh</code> lives is
used.
</P>
<P>
<TABLE id="Table1" cellSpacing="1" cellPadding="1" width="100%" border="1">
<TR>
<TD><STRONG>Variable Name</STRONG></TD>
<TD><STRONG>Semantics</STRONG></TD>
<TD><STRONG>Defaults</STRONG></TD>
<TD><STRONG>Notes</STRONG></TD>
</TR>
<TR>
<TD><CODE>INTEL_VERSION</CODE></TD>
<TD>The version of the compiler to use.</TD>
<TD>80</TD>
<TD>If <CODE>INTEL_PATH</CODE> is set, this variable is ignored.</TD>
</TR>
<TR>
<TD>INTEL_PATH</TD>
<TD>The path to the compiler installation.</TD>
<TD>The default installation location for the version specified by <CODE>INTEL_VERSION.</CODE></TD>
<TD></TD>
</TR>
<TR>
<TD>INTEL_CC</TD>
<TD>The name of the C compiler.</TD>
<TD>icc</TD>
<TD></TD>
</TR>
<TR>
<TD>INTEL_CXX</TD>
<TD>The name of the C++ compiler/linker.</TD>
<TD>icpc</TD>
<TD></TD>
</TR>
</TABLE>
</P>
<hr>
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
01 Oct, 2004 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Copyright &copy; Dave Abrahams 2002-2003.</p>
<p><small>Use, modification, and distribution are subject to the Boost Software
License, Version 1.0. (See accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a>
or copy at <a href="http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
<head>
<title>Boost.Build - intel-linux toolset</title>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 1st September 2003), see www.w3.org">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="../../../boost.css">
</head>
<body link="#0000FF" vlink="#800080">
<table border="0" cellpadding="7" cellspacing="0" width="100%" summary=
"header">
<tr>
<td valign="top" width="300">
<h3><a href="http://www.boost.org"><img height="86" width="277" alt=
"C++ Boost" src="../../../c++boost.gif" border="0"></a></h3>
</td>
<td valign="top">
<h1 align="center">Boost.Build</h1>
<h2 align="center">intel-linux toolset</h2>
</td>
</tr>
</table>
<hr>
<h2>Introduction</h2>
<p>Boost.Build's intel-linux toolset supports the <a href=
"http://www.intel.com/software/products/compilers/clin/index.htm">Intel C++
Compiler for Linux</a>.</p>
<h2>Configuration Variables</h2>
<p>The intel-linux toolset responds to the following variables which can be
set in the environment or configured on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. If neither variable is
set but <code>iccvars.sh</code> can be found in the <code>PATH</code>, then
the version of the tools installed where <code>iccvars.sh</code> lives is
used.</p>
<table id="Table1" cellspacing="1" cellpadding="1" width="100%" border="1">
<tr>
<td><strong>Variable Name</strong></td>
<td><strong>Semantics</strong></td>
<td><strong>Defaults</strong></td>
<td><strong>Notes</strong></td>
</tr>
<tr>
<td><code>INTEL_VERSION</code></td>
<td>The version of the compiler to use.</td>
<td>80</td>
<td>If <code>INTEL_PATH</code> is set, this variable is ignored.</td>
</tr>
<tr>
<td>INTEL_PATH</td>
<td>The path to the compiler installation.</td>
<td>The default installation location for the version specified by
<code>INTEL_VERSION.</code></td>
<td></td>
</tr>
<tr>
<td>INTEL_CC</td>
<td>The name of the C compiler.</td>
<td>icc</td>
<td></td>
</tr>
<tr>
<td>INTEL_CXX</td>
<td>The name of the C++ compiler/linker.</td>
<td>icpc</td>
<td></td>
</tr>
</table>
<hr>
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
01 Oct, 2004 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Copyright &copy; Dave Abrahams 2002-2003.</p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

8
v1/intel-linux-tools.jam
View File

@@ -1,8 +1,6 @@
# (C) Copyright David Abrahams 2001. Permission to copy, use
# modify, sell and distribute this software is granted provided this
# copyright notice appears in all copies. This software is provided
# "as is" without express or implied warranty, and with no claim as
# to its suitability for any purpose.
# (C) Copyright David Abrahams 2001.
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
# Adapted from gcc-tools.jam by Joerg Walter

6
v1/intel-win32-tools.html
View File

@@ -107,9 +107,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

6
v1/kcc-tools.html
View File

@@ -72,9 +72,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

5
v1/kylix-tools.html
View File

@@ -79,5 +79,10 @@
<p><i>&copy; Copyright</i> <a href="mailto:john@johnmaddock.co.uk"><i>John
Maddock</i></a><i>2002. All Rights Reserved.</i></p>
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

29
v1/mingw-stlport-tools.html
View File

@@ -35,15 +35,15 @@
"http://www.stlport.org">STLport</a> as a replacement to the GNU
libg++.</p>
<h2><a name="configuration">Configuration Variables</a></h2>The
mingw-stlport toolset responds to the following variables which can be
set in the environment or configured on the jam command-line using
<span style="white-space:nowrap;"><code>-s<i>VARIABLE_NAME</i>=</code><i>value</i></span>.
This toolset is an
extension to the <a href="mingw-tools.html">mingw toolset</a> and
therefore responds to all of the MinGW <a href=
"mingw-tools.html#configuration">configuration variables</a> in addition
to those listed below.
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The mingw-stlport toolset responds to the following
variables which can be set in the environment or configured on the jam
command-line using <span style=
"white-space:nowrap;"><code>-s<i>VARIABLE_NAME</i>=</code><i>value</i></span>.
This toolset is an extension to the <a href="mingw-tools.html">mingw
toolset</a> and therefore responds to all of the MinGW <a href=
"mingw-tools.html#configuration">configuration variables</a> in addition to
those listed below.
<table border="1" summary="settings">
<tr>
@@ -90,15 +90,16 @@
</table>
<hr>
<p>Revised
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
12 August, 2004 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
12 August, 2004
<!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p>Copyright &copy; Janusz Piwowarski 2004.</p>
<p><small>Distributed under the Boost Software License, Version 1.0.
(See accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

6
v1/mingw-tools.html
View File

@@ -99,9 +99,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

6
v1/mipspro-tools.html
View File

@@ -113,9 +113,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

25
v1/msvc-stlport-tools.html
View File

@@ -41,13 +41,14 @@
that objects build in each configuration will be built into separate
directories.</p>
<h2><a name="configuration">Configuration Variables</a></h2>The
<code>msvc</code> toolset responds to the following variables, which can be
set in the environment or configured on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is an extension of the
<a href="msvc-tools.html">msvc toolset</a> and therefore responds to all of
the MSVC <a href="msvc-tools.html#configuration">configuration
variables</a> in addition to those listed below.
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The <code>msvc</code> toolset responds to the following
variables, which can be set in the environment or configured on the jam
command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is
an extension of the <a href="msvc-tools.html">msvc toolset</a> and
therefore responds to all of the MSVC <a href=
"msvc-tools.html#configuration">configuration variables</a> in addition to
those listed below.
<p>In the table below, <i>version</i> corresponds to an STLPort version
number, e.g. "<code>4.5.3</code>".</p>
@@ -112,8 +113,8 @@
</tr>
</table>
<h2><a name="features">Toolset-Specific Features</a></h2>The following
<code>msvc-stlport</code>-specific <a href=
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>The
following <code>msvc-stlport</code>-specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:
@@ -171,9 +172,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

14
v1/msvc-tools.html
View File

@@ -37,10 +37,10 @@
additional <a href="vc7-tools.html">vc7</a> toolset can be used for Visual
C++ 7.0.</p>
<h2><a name="configuration">Configuration Variables</a></h2>The
<code>msvc</code> toolset responds to the following variables, which can be
set in the environment or configured on the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The <code>msvc</code> toolset responds to the following
variables, which can be set in the environment or configured on the jam
command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>:
<table border="1" summary="settings">
<tr>
@@ -85,9 +85,9 @@
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
14 May, 2002 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

144
v1/sunpro-tools.html
View File

@@ -31,96 +31,115 @@
<h2>Introduction</h2>
<p>Boost.Build's <code>sunpro</code> toolset supports the <a href=
"http://wwws.sun.com/software/sundev/suncc/index.html"
>Sun ONE Studio</a> compiler. This compiler has been known under
several trade names including Sun WorkShop and Forte Developer. For
convenience, this document will refer to numbered releases of the
compiler when differention is neccessary; this release number can be
obtained by running <code>CC &#8209;V</code> at the command line.</p>
"http://wwws.sun.com/software/sundev/suncc/index.html">Sun ONE Studio</a>
compiler. This compiler has been known under several trade names including
Sun WorkShop and Forte Developer. For convenience, this document will refer
to numbered releases of the compiler when differention is neccessary; this
release number can be obtained by running <code>CC &#8209;V</code> at the
command line.</p>
<h2>Compatibility</h2>
<p>As of this writing (November 2003) the Sun C++ compiler has
difficulty building many of the libraries included with Boost. <a
href="http://boost.sourceforge.net/regression-logs/cs-SunOS.html"
>Complete regression test information is available</a>, although
absent from the regression tables are some libraries that Sun C++
has particular difficulty with, including <code><a href=
"../../../libs/mpl/doc/index.html">mpl</a></code> and
<code><a href="../../../libs/spirit/index.html">spirit</a></code>.
<p>As of this writing (November 2003) the Sun C++ compiler has difficulty
building many of the libraries included with Boost. <a href=
"http://boost.sourceforge.net/regression-logs/cs-SunOS.html">Complete
regression test information is available</a>, although absent from the
regression tables are some libraries that Sun C++ has particular difficulty
with, including <code><a href=
"../../../libs/mpl/doc/index.html">mpl</a></code> and <code><a href=
"../../../libs/spirit/index.html">spirit</a></code>.</p>
<h3>Notes on specific versions</h3>
<p>Best results can be obtained by being up-to-date on the most
recent patches for your compiler version. Information on patches
is <a href="http://access1.sun.com/sundev/index.html"
>available from Sun Microsystems.</a>
<p>Best results can be obtained by being up-to-date on the most recent
patches for your compiler version. Information on patches is <a href=
"http://access1.sun.com/sundev/index.html">available from Sun
Microsystems.</a></p>
<p style="text-align: center">&nbsp;</p>
<p style="text-align: center">
<table border="1" summary="Version notes">
<tr>
<th>Compiler Version</th>
<th>Trade Name(s)</th>
<th>Notes</th>
</tr>
<tr>
<td>&lt;= 5.2</td>
<td>Sun&nbsp;WorkShop&nbsp;5<br>
Sun&nbsp;WorkShop&nbsp;6<br>
Sun&nbsp;WorkShop&nbsp;6&nbsp;update&nbsp;1</td>
<td><p>No current information available. Boost is unlikely to be
very functional with these older releases, as they do not
support some of the necessary parts of the C++ language.
Patches and workarounds are welcome.</p></td>
Sun&nbsp;WorkShop&nbsp;6<br>
Sun&nbsp;WorkShop&nbsp;6&nbsp;update&nbsp;1</td>
<td>
<p>No current information available. Boost is unlikely to be very
functional with these older releases, as they do not support some of
the necessary parts of the C++ language. Patches and workarounds are
welcome.</p>
</td>
</tr>
<tr>
<td>5.3</td>
<td>Sun&nbsp;WorkShop&nbsp;6&nbsp;update&nbsp;2</td>
<td><p>The most recent reports seem to imply that this release is
<a href=
"http://article.gmane.org/gmane.comp.lib.boost.devel/27660"
>&ldquo;hopeless for Boost&rdquo;</a>, but patches and
workarounds are welcome.</p>
<td>
<p>The most recent reports seem to imply that this release is
<a href="http://article.gmane.org/gmane.comp.lib.boost.devel/27660">&ldquo;hopeless
for Boost&rdquo;</a>, but patches and workarounds are welcome.</p>
</td>
</tr>
<tr>
<td>5.4</td>
<td>Forte&nbsp;Developer&nbsp;7</td>
<td><p>This version recognizes an undocumented, unsupported flag
that improves its success in compiling templates:</p>
<blockquote><code>&#8209;Qoption CC
&#8209;xcomdat</code></blockquote>
<td>
<p>This version recognizes an undocumented, unsupported flag that
improves its success in compiling templates:</p>
<p>This flag changes the template instantiation method from
&ldquo;exported&rdquo; to an improved &ldquo;global&rdquo;
which has been found to eliminate some compiler bugs
regarding the instantiation of template run-time type
information. This option, if used, is required for both
compiling and linking.</p>
<blockquote>
<code>&#8209;Qoption CC &#8209;xcomdat</code>
</blockquote>
<p>This flag changes the template instantiation method from
&ldquo;exported&rdquo; to an improved &ldquo;global&rdquo; which has
been found to eliminate some compiler bugs regarding the
instantiation of template run-time type information. This option, if
used, is required for both compiling and linking.</p>
</td>
</tr>
<tr>
<td>5.5</td>
<td>Sun ONE Studio 8</td>
<td><p>No current information is available. This version changes
the default template instantiation method from
&ldquo;exported&rdquo; (using a template repository) to
&ldquo;global&rdquo; (storing instances in object files
with global linkage). The linker should then automatically
detect and eliminate duplicate definitions. This change
<i>should</i> improve template performace over previous
releases.</p>
<td>
<p>No current information is available. This version changes the
default template instantiation method from &ldquo;exported&rdquo;
(using a template repository) to &ldquo;global&rdquo; (storing
instances in object files with global linkage). The linker should
then automatically detect and eliminate duplicate definitions. This
change <i>should</i> improve template performace over previous
releases.</p>
</td>
</tr>
</tr>
</table>
</p>
<h2>Configuration Variables</h2>
<p>The sunpro toolset responds to the following variables which can
be set in the environment or configured on the bjam command line using
<p>The sunpro toolset responds to the following variables which can be set
in the environment or configured on the bjam command line using
<code>&#8209;s<i>VARIABLE_NAME</i>=</code><i>value</i>:</p>
<p style="text-align: center">
<p style="text-align: center">&nbsp;</p>
<table border="1" summary="settings">
<tr>
<th>Variable Name</th>
@@ -139,10 +158,10 @@
<td>(none)</td>
<td>Usually there is no need to set this variable at all.
However, if <code>CC</code> is not in the path is is usually
sufficient to configure this one variable. A typical value
for this variable is <code>/opt/SUNWspro</code>.</td>
<td>Usually there is no need to set this variable at all. However, if
<code>CC</code> is not in the path is is usually sufficient to
configure this one variable. A typical value for this variable is
<code>/opt/SUNWspro</code>.</td>
</tr>
<tr>
@@ -163,10 +182,10 @@
<td><code>$(SUNPRO_BIN_DIRECTORY)CC</code></td>
<td>You can also use this in lieu of setting the &lt;cxxflags&gt;
property to force options such as <code>&#8209;Qoption CC
&#8209;xcomdat</code> into the CC command line:
<code>&ldquo;&#8209;sSUNPRO_CXX=CC &#8209;Qoption CC
&#8209;xcomdat&rdquo;</code>.</td>
property to force options such as <code>&#8209;Qoption CC
&#8209;xcomdat</code> into the CC command line:
<code>&ldquo;&#8209;sSUNPRO_CXX=CC &#8209;Qoption CC
&#8209;xcomdat&rdquo;</code>.</td>
</tr>
<tr>
@@ -178,10 +197,7 @@
<td>&nbsp;</td>
</tr>
</table>
</p>
<hr>
<p>Revised

6
v1/tru64cxx-tools.html
View File

@@ -58,9 +58,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

6
v1/vacpp-tools.html
View File

@@ -45,9 +45,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

6
v1/variables.html
View File

@@ -481,9 +481,9 @@
<p>Copyright &copy; Rene Rivera 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

17
v1/vc7-stlport-tools.html
View File

@@ -40,9 +40,10 @@
that objects build in each configuration will be built into separate
directories.</p>
<h2><a name="configuration">Configuration Variables</a></h2>The
<code>vc7-stlport</code> toolset responds to the following variables, which
can be set in the environment or configured on the jam command-line using
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The <code>vc7-stlport</code> toolset responds to the
following variables, which can be set in the environment or configured on
the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is an extension of the
<a href="msvc-stlport-tools.html">msvc-stlport toolset</a> and therefore
responds to all of the MSVC <a href=
@@ -112,8 +113,8 @@
</tr>
</table>
<h2><a name="features">Toolset-Specific Features</a></h2>The following vc7
<code>-stlport</code>-specific <a href=
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>The
following vc7 <code>-stlport</code>-specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:
@@ -175,9 +176,9 @@
<p>Copyright &copy; John Maddock 2003.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

6
v1/vc7-tools.html
View File

@@ -72,9 +72,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

23
v1/vc7.1-stlport-tools.html
View File

@@ -40,12 +40,13 @@
multiple installed versions of STLPort, so that objects build in each
configuration will be built into separate directories.</p>
<h2><a name="configuration">Configuration Variables</a></h2>The
<code>vc7.1-stlport</code> toolset responds to the following variables,
which can be set in the environment or configured on the jam command-line
using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is an extension
of the <a href="msvc-stlport-tools.html">msvc-stlport toolset</a> and
therefore responds to all of the MSVC <a href=
<h2><a name="configuration" id="configuration">Configuration
Variables</a></h2>The <code>vc7.1-stlport</code> toolset responds to the
following variables, which can be set in the environment or configured on
the jam command-line using
<code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. It is an extension of the
<a href="msvc-stlport-tools.html">msvc-stlport toolset</a> and therefore
responds to all of the MSVC <a href=
"msvc-tools.html#configuration">configuration variables</a> in addition to
those listed below.
@@ -112,8 +113,8 @@
</tr>
</table>
<h2><a name="features">Toolset-Specific Features</a></h2>The following vc7
<code>-stlport</code>-specific <a href=
<h2><a name="features" id="features">Toolset-Specific Features</a></h2>The
following vc7 <code>-stlport</code>-specific <a href=
"build_system.htm#features">features</a> can be used in target build
requirements or in the <a href=
"build_system.htm#initiating"><code>BUILD</code></a> variable:
@@ -175,9 +176,9 @@
<p>Copyright &copy; John Maddock 2003.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>

6
v1/vc7.1-tools.html
View File

@@ -73,9 +73,9 @@
<p>Copyright &copy; Dave Abrahams 2002.</p>
<p><small>Use, modification, and distribution are subject to the Boost
Software License, Version 1.0. (See accompanying file <a href=
"../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or copy at <a href=
<p><small>Distributed under the Boost Software License, Version 1.0. (See
accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
copy at <a href=
"http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</small></p>
</body>
</html>