From bb4d03e57ec6cfa4b91731cc90da7ef051380d2d Mon Sep 17 00:00:00 2001 From: Rene Rivera Date: Sun, 3 Oct 2004 16:27:43 +0000 Subject: [PATCH] Clneaup... Update license statements and HTMLTidy. [SVN r25538] --- v1/acc-tools.jam | 7 +- v1/borland-tools.html | 6 +- v1/build_system.htm | 193 +++++++++++++++++++----------------- v1/como-tools.html | 22 ++-- v1/cw-tools.html | 90 +++++++++-------- v1/darwin-tools.html | 16 +-- v1/dmc-stlport-tools.html | 52 +++++----- v1/dmc-tools.html | 31 +++--- v1/edg-tools.html | 5 + v1/gcc-nocygwin-tools.html | 5 +- v1/gcc-stlport-tools.html | 18 ++-- v1/gcc-stlport-tools.jam | 8 +- v1/gcc-tools.html | 14 +-- v1/index.html | 18 +++- v1/intel-linux-tools.html | 180 +++++++++++++++++++-------------- v1/intel-linux-tools.jam | 8 +- v1/intel-win32-tools.html | 6 +- v1/kcc-tools.html | 6 +- v1/kylix-tools.html | 5 + v1/mingw-stlport-tools.html | 29 +++--- v1/mingw-tools.html | 6 +- v1/mipspro-tools.html | 6 +- v1/msvc-stlport-tools.html | 25 ++--- v1/msvc-tools.html | 14 +-- v1/sunpro-tools.html | 144 +++++++++++++++------------ v1/tru64cxx-tools.html | 6 +- v1/vacpp-tools.html | 6 +- v1/variables.html | 6 +- v1/vc7-stlport-tools.html | 17 ++-- v1/vc7-tools.html | 6 +- v1/vc7.1-stlport-tools.html | 23 +++-- v1/vc7.1-tools.html | 6 +- 32 files changed, 537 insertions(+), 447 deletions(-) diff --git a/v1/acc-tools.jam b/v1/acc-tools.jam index 5317ff230..12eecfce4 100644 --- a/v1/acc-tools.jam +++ b/v1/acc-tools.jam @@ -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 : diff --git a/v1/borland-tools.html b/v1/borland-tools.html index 68c50edd3..4289b928e 100644 --- a/v1/borland-tools.html +++ b/v1/borland-tools.html @@ -74,9 +74,9 @@

Copyright © Dave Abrahams 2002.

-

Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

diff --git a/v1/build_system.htm b/v1/build_system.htm index 65ca6276d..6f768c0e6 100644 --- a/v1/build_system.htm +++ b/v1/build_system.htm @@ -29,7 +29,7 @@ -

Synopsis

+

Synopsis

Boost.Build is a system for large project software construction built on Boost.Jam, a descendant of "Automatic building of subproject dependencies -

Status

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 Boost.Build v2, 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 StatusBoost.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 Boost.Build v2, 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 jamboost mailing list at yahoogroups. @@ -186,14 +186,14 @@
  • Footnotes
    • -

    Getting Started

    +

    Getting Started

    -

    Installing Boost.Jam

    Follow these - instructions to - acquire a bjam executable for your platform. Install it somewhere in your - path. +

    Installing + Boost.Jam

    Follow these instructions to acquire a + bjam executable for your platform. Install it somewhere in your path. -

    Initiating a Build

    +

    Initiating a Build

    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" -

    Setting Jam Variables

    +

    Setting Jam + Variables

    The "-s" 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. -

    An Example Jamfile

    Here is an example - of a simple subproject Jamfile. In this example, it is assumed that the - user has set BOOST_ROOT, either as an environment variable, on the - command-line or in the project's Jamrules - file: +

    An Example + Jamfile

    Here is an example of a simple subproject Jamfile. In this + example, it is assumed that the user has set BOOST_ROOT, either as + an environment variable, on the command-line or in the project's + Jamrules file: 
    @@ -362,7 +363,7 @@ subinclude foo/bar/baz foo/bar/... ;
    -

    Support Files

    +

    Support Files

    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 foo/bar/... ; The boost-base.jam file is temporary, and will eventually be compiled into our Jam executable. -

    Basic Design and Terminology

    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. +

    Basic Design and Terminology

    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. -

    Projects and Subprojects

    +

    Projects and + Subprojects

    A project is a source directory tree containing at least one Jamfile. The root directory of the project is known as the - project root. The root directory of a project - may contain a Jamrules file, which contains project-specific Jam - code. If the Jamrules file is not present when Jam is invoked, a - warning will be issued.

    + project root. The root + directory of a project may contain a Jamrules file, which contains + project-specific Jam code. If the Jamrules file is not present + when Jam is invoked, a warning will be issued.

    Subdirectories containing Jamfiles are called subproject directories. Each such Jamfile describes a @@ -426,15 +428,14 @@ subinclude foo/bar/baz foo/bar/... ;

    The build system installation directory is a directory containing Jam files describing compilers and build variants. The installation directory can be specified in a file called boost-build.jam in the - project root directory. This file should contain a line - boost-build $path-to-installation-dir. If no such file is - available the environment variable - BOOST_BUILD_PATH 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 - BOOST_BUILD_PATH is set to include that directory.

    + project root directory. This file should contain a line boost-build + $path-to-installation-dir. If no such file is available the + environment variable BOOST_BUILD_PATH 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 BOOST_BUILD_PATH is set to include that directory.

    -

    Targets

    +

    Targets

    Each Jamfile describes one or more main targets.

    @@ -453,7 +454,7 @@ subinclude foo/bar/baz foo/bar/... ; directory can be customized by changing the BIN_DIRECTORY variable. -
  • If the variable +
  • If the variable ALL_LOCATE_TARGET is set, 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 foo/bar/... ; directory tree known as the target's build root, where all intermediate and final targets resulting from that main target are located. -

    Features and Properties

    +

    Features and Properties

    A feature 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 foo/bar/... ; property. The prefixes simple, free, path, and dependency apply to properties in an analogous way to features.

    -

    Build Variants

    +

    Build Variants

    A build variant, or simply variant 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 foo/bar/... ; so debug may mean a slightly different set of properties for two different compilers.

    -

    Subvariants

    +

    Subvariants

    When a target is built with simple 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 foo/bar/... ; base variant or subvariant, is known as a build configuration, or simply a build.

    -

    Dependent Targets

    +

    Dependent Targets

    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 foo/bar/... ; compilation units. This danger can be minimized by encapsulating such feature differences inside of build variants.

    -

    Usage

    +

    Usage

    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.

    -

    The Command Line

    +

    The Command Line

    This section describes in detail how the build system can be invoked.

    -

    User Targets

    +

    User Targets

    The Jam command line ends with an optional list of target names; if no target names are supplied, the built-in pseudotarget all is built. @@ -676,7 +677,7 @@ exe my_target : my_source1.cpp my_source2.c ; Please see this section for a more complete description of how to name particular targets in a build.

    -

    Global Variables

    +

    Global Variables

    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 ; - TOOLS + TOOLS Platform-dependent @@ -714,7 +715,7 @@ exe my_target : my_source1.cpp my_source2.c ; - BUILD + BUILD @@ -760,9 +761,11 @@ exe my_target : my_source1.cpp my_source2.c ; This section describes how to write a Jamfile for a subproject. -

    SubProject Jamfiles

    +

    SubProject + Jamfiles

    -

    The subproject rule

    +

    The subproject + rule

    A subproject's Jamfile begins with an invocation of the subproject rule that specifies the subproject's location relative @@ -785,7 +788,8 @@ project-root ; -

    Describing Main Targets

    +

    Describing Main + Targets

    A main target is described using the following syntax:

    @@ -821,8 +825,8 @@ project-root ;
  • sources is a list of paths to source files and dependency - targets. The syntax for dependency targets is - described by the following grammar: + targets. The syntax for + dependency targets is described by the following grammar: 
    @@ -859,9 +863,10 @@ project-root ;
  • - requirements specifies the - build properties intrinsic to the target. Requirements are given as - sets of optionally-qualified build properties: + requirements specifies the build + properties intrinsic to the target. Requirements are given as sets of + optionally-qualified build properties: 
    @@ -879,8 +884,8 @@ project-root ;
  • - default-BUILD specifies the - configurations that should be built if the default-BUILD + specifies the configurations that should be built if the BUILD variable is not otherwise specified. Any elements not beginning with ``<...>'' refer to build variants. Other elements use the same syntax as the default-BUILD, more-specific qualification overrides less-specific.

    -

    Describing Template Targets

    +

    Describing Template + Targets

    Template targets provide a way to handle commonalities between projects targets. They have the same form as main @@ -933,7 +939,8 @@ exe test : test.cpp <lib>basic ; defines, include paths and additional compiler flags common to all targets in the project.

    -

    Describing Stage Targets

    +

    Describing Stage + Targets

    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 <lib>basic ; target.

    • -

    Example

    +

    Example

    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 : <template>executable fop.cpp ; and dynamically-linked subvariants of the debug variant. -

    Using External Projects

    To use - dependencies such as libraries from another project tree, first use the - project rule to declare a project id and location for the - external project. Then add the appropriate external dependency target specification to your program's list of - sources. For example, if you are developing a program which uses the - Boost.Threads library, you might write +

    Using External + Projects

    To use dependencies such as libraries from another project + tree, first use the project rule to declare a project id and + location for the external project. Then add the appropriate external + dependency target specification to your program's + list of sources. For example, if you are developing a program which uses + the Boost.Threads library, you might write 
    @@ -1076,7 +1083,8 @@ project boost : /home/dave/boost-cvs ;
    in your target's list of sources. -

    Requirement Rules

    +

    Requirement + Rules

    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 ; -

    Install Descriptions

    +

    Install + Descriptions

    Installable files and targets are described with:

    @@ -1201,7 +1210,8 @@ install name type : sources... : [options]... ;
    -

    Feature Descriptions

    +

    Feature + Descriptions

    Features are described by stating the feature type (simple features are specified with "feature"), followed by the feature name. An @@ -1209,7 +1219,8 @@ install name type : sources... : [options]... ; feature. Examples can be found in features.jam.

    -

    Variant Descriptions

    +

    Variant + Descriptions

    Variants are described with the following syntax:

    @@ -1238,7 +1249,8 @@ variant my-release : my-globals release ; More examples can be found in features.jam. -

    Toolset Description Files

    +

    Toolset + Description Files

    Toolset descriptions are located in the project's root directory, or a directory specified by BOOST_BUILD_INSTALLATION, which may be set @@ -1340,7 +1352,7 @@ flags toolset variable condition [: value...] -

    Example

    +

    Example

    The description of the flags rule above is actually more complicated than it sounds. For example, the following line might be used @@ -1374,9 +1386,9 @@ flags msvc HDRS <include> ;

    The use of these variables should be apparent from the declaration of actions msvc-C++-action in the previous section.

    -

    Internals

    +

    Internals

    -

    Target Names

    +

    Target Names

    In addition to user targets, which correspond directly to the names the user writes in her subproject Jamfile, @@ -1404,7 +1416,8 @@ flags msvc HDRS <include> ; targets will be identified this way. -

    Global Variables

    +

    Global + Variables

    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 <include> ; subproject!id/target/toolset/variant/subvariant-path. -

    Design Criteria

    +

    Design Criteria

    -

    Assumptions

    +

    Assumptions

    The requirements are driven by several basic assumptions:

    @@ -1476,7 +1489,7 @@ flags msvc HDRS <include> ; compilers that almost no other assumptions can be made. -

    Requirements

    +

    Requirements

    This build system was designed to satisfy the following requirements:

    @@ -1525,16 +1538,16 @@ flags msvc HDRS <include> ; the source directories (they may be read-only) -

    Footnotes

    [1] Boost Jam is - actually descended directly from Footnotes[1] Boost Jam is actually descended directly from FTJam, which was itself a variant of Jam/MR. It is hoped that crucial features we rely on will eventually be incorporated back into the Jam/MR release. -

    [2] Note: right now, a dependency feature of a main - target makes all resulting built targets dependent, including +

    [2] Note: right now, a dependency feature of a + main target makes all 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 <include> ;

    Revised 8 September, 2003 -

    Copyright © Dave Abrahams 2001.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/como-tools.html b/v1/como-tools.html index 199ec81b6..52d702d7d 100644 --- a/v1/como-tools.html +++ b/v1/como-tools.html @@ -33,12 +33,12 @@

    Boost.Build's como and como-win32 toolsets support the Comeau Computing C/C++ Compiler.

    -

    Configuration Variables

    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 - -sVARIABLE_NAME=value: -

    - +

    Configuration Variables

    + +

    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 -sVARIABLE_NAME=value:

    + @@ -104,7 +104,8 @@ - + @@ -120,7 +121,6 @@ -
    Variable Name
    COMO_BACKENDBackend abbreviation, e.g. vc7, bcc, dig, etc.Backend abbreviation, e.g. vc7, bcc, + dig, etc. vc7como-win32 toolset only.
    @@ -131,9 +131,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/cw-tools.html b/v1/cw-tools.html index 0d7542e9a..97ae0545e 100644 --- a/v1/cw-tools.html +++ b/v1/cw-tools.html @@ -22,8 +22,7 @@

    Boost.Build

    - -

    cw toolset

    +

    cw toolset

    @@ -31,52 +30,59 @@

    Introduction

    - -

    Boost.Build's cw toolset supports the Metrowerks CodeWarrior Pro 6.x, 7.x, 8.x and - 9.x tools. This toolsets handles allteh variations for the CodeWarrior command - line compiler tools.

    +

    Boost.Build's cw toolset supports the Metrowerks CodeWarrior Pro 6.x, 7.x, 8.x + and 9.x tools. This toolsets handles allteh variations for the CodeWarrior + command line compiler tools.

    -

    Configuration Variables

    -The cw toolset responds to the following variables which can be set in the environment -or configured on the jam command-line using -sVARIABLE_NAME=value: - - - - - - - - - - - - - - - - - - -
    Variable NameSemanticsDefaultNotes
    CW_ROOTPath to installation of Metrowerks Codewarrior.emptyThe 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.
    CW_VERSIONVersion to use. Valid values are: 6.0, 7.0, 8.0, 9.0.empty
    +

    Configuration Variables

    The cw toolset responds to the following + variables which can be set in the environment or configured on the jam + command-line using -sVARIABLE_NAME=value: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Variable NameSemanticsDefaultNotes
    CW_ROOTPath to installation of Metrowerks Codewarrior.emptyThe 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.
    CW_VERSIONVersion to use. Valid values are: 6.0, 7.0, 8.0, 9.0.empty
    - -

    Revised +

    Revised - 23 February, 2004 - -

    + 23 February, 2004 +

    - -

    Copyright Rene Rivera 2004.

    +

    Copyright Rene Rivera 2004.

    - -

    Distributed under the Boost Software License, Version 1.0. (See accompanying - file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/darwin-tools.html b/v1/darwin-tools.html index 9368f965e..9ab6f4ebd 100644 --- a/v1/darwin-tools.html +++ b/v1/darwin-tools.html @@ -36,12 +36,12 @@ tailored to account for the various "features" that Apple implemented to work in the Darwin OS Mach kernel.

    -

    Configuration Variables

    Because of the - already specific nature of this toolset there are no additional - configuration variables. +

    Configuration + Variables

    Because of the already specific nature of this toolset + there are no additional configuration variables. -

    Toolset-Specific Features

    The following - darwin-specific Toolset-Specific FeaturesThe + following darwin-specific features can be used in target build requirements or in the BUILD variable: @@ -89,9 +89,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/dmc-stlport-tools.html b/v1/dmc-stlport-tools.html index 2659f21b2..d268e9406 100644 --- a/v1/dmc-stlport-tools.html +++ b/v1/dmc-stlport-tools.html @@ -32,24 +32,24 @@

    Introduction

    -

    Boost.Build's dmc-stlport - toolset supports the Digital Mars C++ +

    Boost.Build's dmc-stlport toolset + supports the Digital Mars C++ command-line tools, using the STLport - 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.

    + 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.

    + +

    Configuration + Variables

    + +

    The dmc-stlport toolset responds to the following + variables, which can be set in the environment or configured on the jam + command-line using -sVARIABLE_NAME=value. It is + an extension of the dmc toolset and therefore + responds to all of the Digital Mars configuration variables in addition to + those listed below.

    -

    Configuration Variables

    -

    The - dmc-stlport toolset responds to the following variables, which can be - set in the environment or configured on the jam command-line using - -sVARIABLE_NAME=value. It is an extension of the - dmc toolset and therefore responds to all of - the Digital Mars configuration - variables in addition to those listed below. -

    -

    In the table below, version corresponds to an STLPort version number, e.g. "4.5.3".

    @@ -113,14 +113,13 @@ -

    Toolset-Specific Features

    -

    The following - dmc-stlport-specific Toolset-Specific Features + +

    The following dmc-stlport-specific features can be used in target build requirements or in the BUILD variable: -

    - + "build_system.htm#initiating">BUILD variable:

    + @@ -170,13 +169,14 @@

    Revised - 31 July, 2004

    + 31 July, 2004 +

    Copyright © Dave Abrahams 2002, Aleksey Gurtovoy 2004.

    -

    Distributed under the Boost Software License, Version 1.0. - (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    - diff --git a/v1/dmc-tools.html b/v1/dmc-tools.html index a7ce6ddd4..1d214d956 100644 --- a/v1/dmc-tools.html +++ b/v1/dmc-tools.html @@ -30,16 +30,17 @@

    Introduction

    -

    Boost.Build's dmc toolset supports the - Digital Mars C++ command-line tools.

    +

    Boost.Build's dmc toolset supports the + Digital Mars C++ command-line + tools.

    + +

    Configuration + Variables

    + +

    The dmc toolset responds to the following variables, which + can be set in the environment or configured on the jam command-line using + -sVARIABLE_NAME=value:

    -

    Configuration Variables

    -

    The - dmc toolset responds to the following variables, which can be - set in the environment or configured on the jam command-line using - -sVARIABLE_NAME=value: -

    -
    Feature
    @@ -56,23 +57,23 @@ - + -
    Variable NameThe path to the Digital Mars C++ installation directory - emptyempty For example, C:\Program Files\Digital Mars

    Revised - 31 July, 2004

    + 31 July, 2004 +

    Copyright © Dave Abrahams 2002, Aleksey Gurtovoy 2004.

    -

    Distributed under the Boost Software License, Version 1.0. - (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/edg-tools.html b/v1/edg-tools.html index 4f813a005..d03e00eab 100644 --- a/v1/edg-tools.html +++ b/v1/edg-tools.html @@ -68,5 +68,10 @@

    Written by Jens Maurer.

    + +

    Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/gcc-nocygwin-tools.html b/v1/gcc-nocygwin-tools.html index 09cb24d76..98fb24753 100644 --- a/v1/gcc-nocygwin-tools.html +++ b/v1/gcc-nocygwin-tools.html @@ -43,7 +43,8 @@ using Cygwin, this toolset could save you having to install an additional compiler.

    -

    Configuration Variables

    +

    Configuration + Variables

    This toolset operates in one of two modes - the default mode (which is recommended) just extends the gcc toolset -

    STLport iostream support

    +

    STLport iostream support

    Here's the procedure for using the STLport iostream libraries with gcc-nocygwin:

    diff --git a/v1/gcc-stlport-tools.html b/v1/gcc-stlport-tools.html index 765114bf0..88b275f2f 100644 --- a/v1/gcc-stlport-tools.html +++ b/v1/gcc-stlport-tools.html @@ -35,12 +35,12 @@ "http://www.stlport.org">STLport as a replacement to the GNU libg++.

    -

    Configuration Variables

    The gcc-stlport - toolset responds to the following variables which can be set in the - environment or configured on the jam command-line using - -sVARIABLE_NAME=value. This toolset is an - extension to the gcc toolset and therefore - responds to all of the GCC Configuration + VariablesThe gcc-stlport toolset responds to the following + variables which can be set in the environment or configured on the jam + command-line using -sVARIABLE_NAME=value. This + toolset is an extension to the gcc toolset and + therefore responds to all of the GCC configuration variables in addition to those listed below. @@ -95,9 +95,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/gcc-stlport-tools.jam b/v1/gcc-stlport-tools.jam index 512525e78..12c85867c 100644 --- a/v1/gcc-stlport-tools.jam +++ b/v1/gcc-stlport-tools.jam @@ -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 ; diff --git a/v1/gcc-tools.html b/v1/gcc-tools.html index 6a5f4aa26..099d3295e 100644 --- a/v1/gcc-tools.html +++ b/v1/gcc-tools.html @@ -37,10 +37,10 @@ "http://www.mingw.org">MinGW has its own distinct toolset.

    -

    Configuration Variables

    The gcc toolset - responds to the following variables, which can be set in the environment or - configured on the jam command-line using - -sVARIABLE_NAME=value: +

    Configuration + Variables

    The gcc toolset responds to the following variables, + which can be set in the environment or configured on the jam command-line + using -sVARIABLE_NAME=value: @@ -124,9 +124,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/index.html b/v1/index.html index 8e12976d7..89fd177f1 100644 --- a/v1/index.html +++ b/v1/index.html @@ -1,9 +1,21 @@ + + - + + + + -Automatic redirection failed, please go to -build_system.htm. + Automatic redirection failed, please go to build_system.htm. + +

    Copyright © Dave Abrahams 2002.

    + +

    Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/intel-linux-tools.html b/v1/intel-linux-tools.html index f11a482cb..edb8cd645 100644 --- a/v1/intel-linux-tools.html +++ b/v1/intel-linux-tools.html @@ -1,76 +1,110 @@ + - - Boost.Build - intel-linux toolset - - - - - -
    - - - - -
    -

    C++ Boost

    -     		-

    Boost.Build

    -

    intel-linux toolset

    -
    -
    -

    Introduction

    -

    Boost.Build's intel-linux toolset supports the - Intel C++ Compiler for Linux.

    -

    Configuration Variables

    -

    - The intel-linux toolset responds to the following variables which can be set in - the environment or configured on the jam command-line using -sVARIABLE_NAME=value. - If neither variable is set but iccvars.sh can be found in the PATH, - then the version of the tools installed where iccvars.sh lives is - used. -

    -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Variable NameSemanticsDefaultsNotes
    INTEL_VERSIONThe version of the compiler to use.80If INTEL_PATH is set, this variable is ignored.
    INTEL_PATHThe path to the compiler installation.The default installation location for the version specified by INTEL_VERSION.
    INTEL_CCThe name of the C compiler.icc
    INTEL_CXXThe name of the C++ compiler/linker.icpc
    -

    -
    -

    Revised - - 01 Oct, 2004

    -

    Copyright © Dave Abrahams 2002-2003.

    -

    Use, modification, and distribution are subject to the Boost Software - License, Version 1.0. (See accompanying file LICENSE_1_0.txt - or copy at www.boost.org/LICENSE_1_0.txt)

    - + + Boost.Build - intel-linux toolset + + + + + + + + + + + + +
    +

    +

    +     		+

    Boost.Build

    + +

    intel-linux toolset

    +
    +
    + +

    Introduction

    + +

    Boost.Build's intel-linux toolset supports the Intel C++ + Compiler for Linux.

    + +

    Configuration Variables

    + +

    The intel-linux toolset responds to the following variables which can be + set in the environment or configured on the jam command-line using + -sVARIABLE_NAME=value. If neither variable is + set but iccvars.sh can be found in the PATH, then + the version of the tools installed where iccvars.sh lives is + used.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Variable NameSemanticsDefaultsNotes
    INTEL_VERSIONThe version of the compiler to use.80If INTEL_PATH is set, this variable is ignored.
    INTEL_PATHThe path to the compiler installation.The default installation location for the version specified by + INTEL_VERSION.
    INTEL_CCThe name of the C compiler.icc
    INTEL_CXXThe name of the C++ compiler/linker.icpc
    +
    + +

    Revised + + 01 Oct, 2004

    + +

    Copyright © Dave Abrahams 2002-2003.

    + +

    Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    + diff --git a/v1/intel-linux-tools.jam b/v1/intel-linux-tools.jam index cf4bf081a..e9950888e 100644 --- a/v1/intel-linux-tools.jam +++ b/v1/intel-linux-tools.jam @@ -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 diff --git a/v1/intel-win32-tools.html b/v1/intel-win32-tools.html index 30d32ec98..bb2dec7dc 100644 --- a/v1/intel-win32-tools.html +++ b/v1/intel-win32-tools.html @@ -107,9 +107,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/kcc-tools.html b/v1/kcc-tools.html index 398609ec3..bce46a81c 100644 --- a/v1/kcc-tools.html +++ b/v1/kcc-tools.html @@ -72,9 +72,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/kylix-tools.html b/v1/kylix-tools.html index c5b084865..001fbf37a 100644 --- a/v1/kylix-tools.html +++ b/v1/kylix-tools.html @@ -79,5 +79,10 @@

    © Copyright John Maddock2002. All Rights Reserved.

    + +

    Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/mingw-stlport-tools.html b/v1/mingw-stlport-tools.html index 6cf098589..54b04083e 100644 --- a/v1/mingw-stlport-tools.html +++ b/v1/mingw-stlport-tools.html @@ -35,15 +35,15 @@ "http://www.stlport.org">STLport as a replacement to the GNU libg++.

    -

    Configuration Variables

    The - mingw-stlport toolset responds to the following variables which can be - set in the environment or configured on the jam command-line using - -sVARIABLE_NAME=value. - This toolset is an - extension to the mingw toolset and - therefore responds to all of the MinGW configuration variables in addition - to those listed below. +

    Configuration + Variables

    The mingw-stlport toolset responds to the following + variables which can be set in the environment or configured on the jam + command-line using -sVARIABLE_NAME=value. + This toolset is an extension to the mingw + toolset and therefore responds to all of the MinGW configuration variables in addition to + those listed below. @@ -90,15 +90,16 @@
    -

    Revised +

    Revised - 12 August, 2004

    + 12 August, 2004 +

    Copyright © Janusz Piwowarski 2004.

    -

    Distributed under the Boost Software License, Version 1.0. - (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    - diff --git a/v1/mingw-tools.html b/v1/mingw-tools.html index 5a4ed7e85..a25c8165b 100644 --- a/v1/mingw-tools.html +++ b/v1/mingw-tools.html @@ -99,9 +99,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/mipspro-tools.html b/v1/mipspro-tools.html index c28f47e80..ec40223a2 100644 --- a/v1/mipspro-tools.html +++ b/v1/mipspro-tools.html @@ -113,9 +113,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/msvc-stlport-tools.html b/v1/msvc-stlport-tools.html index 0545e93b2..44b0e3f02 100644 --- a/v1/msvc-stlport-tools.html +++ b/v1/msvc-stlport-tools.html @@ -41,13 +41,14 @@ that objects build in each configuration will be built into separate directories.

    -

    Configuration Variables

    The - msvc toolset responds to the following variables, which can be - set in the environment or configured on the jam command-line using - -sVARIABLE_NAME=value. It is an extension of the - msvc toolset and therefore responds to all of - the MSVC configuration - variables in addition to those listed below. +

    Configuration + Variables

    The msvc toolset responds to the following + variables, which can be set in the environment or configured on the jam + command-line using -sVARIABLE_NAME=value. It is + an extension of the msvc toolset and + therefore responds to all of the MSVC configuration variables in addition to + those listed below.

    In the table below, version corresponds to an STLPort version number, e.g. "4.5.3".

    @@ -112,8 +113,8 @@ -

    Toolset-Specific Features

    The following - msvc-stlport-specific Toolset-Specific FeaturesThe + following msvc-stlport-specific features can be used in target build requirements or in the BUILD variable: @@ -171,9 +172,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/msvc-tools.html b/v1/msvc-tools.html index ff8218efa..c366a09f1 100644 --- a/v1/msvc-tools.html +++ b/v1/msvc-tools.html @@ -37,10 +37,10 @@ additional vc7 toolset can be used for Visual C++ 7.0.

    -

    Configuration Variables

    The - msvc toolset responds to the following variables, which can be - set in the environment or configured on the jam command-line using - -sVARIABLE_NAME=value: +

    Configuration + Variables

    The msvc toolset responds to the following + variables, which can be set in the environment or configured on the jam + command-line using -sVARIABLE_NAME=value: @@ -85,9 +85,9 @@ 14 May, 2002

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/sunpro-tools.html b/v1/sunpro-tools.html index a9415cec8..7866e1b6f 100644 --- a/v1/sunpro-tools.html +++ b/v1/sunpro-tools.html @@ -31,96 +31,115 @@

    Introduction

    Boost.Build's sunpro toolset supports the Sun ONE Studio 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 CC ‑V at the command line.

    + "http://wwws.sun.com/software/sundev/suncc/index.html">Sun ONE Studio + 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 CC ‑V at the + command line.

    Compatibility

    -

    As of this writing (November 2003) the Sun C++ compiler has - difficulty building many of the libraries included with Boost. Complete regression test information is available, although - absent from the regression tables are some libraries that Sun C++ - has particular difficulty with, including mpl and - spirit. +

    As of this writing (November 2003) the Sun C++ compiler has difficulty + building many of the libraries included with Boost. Complete + regression test information is available, although absent from the + regression tables are some libraries that Sun C++ has particular difficulty + with, including mpl and spirit.

    Notes on specific versions

    -

    Best results can be obtained by being up-to-date on the most - recent patches for your compiler version. Information on patches - is available from Sun Microsystems. +

    Best results can be obtained by being up-to-date on the most recent + patches for your compiler version. Information on patches is available from Sun + Microsystems.

    + +

     

    -

    + + + + - + Sun WorkShop 6
    + Sun WorkShop 6 update 1 + +     + + - + + - + + - - +
    Compiler VersionTrade Name(s)Notes
    <= 5.2Sun WorkShop 5
    - Sun WorkShop 6
    - Sun WorkShop 6 update 1

    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.

    		 +

    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.

    +
    5.3Sun WorkShop 6 update 2

    The most recent reports seem to imply that this release is - “hopeless for Boost”, but patches and - workarounds are welcome.

    + +     		+

    The most recent reports seem to imply that this release is + “hopeless + for Boost”, but patches and workarounds are welcome.

    +
    5.4Forte Developer 7

    This version recognizes an undocumented, unsupported flag - that improves its success in compiling templates:

    -
    ‑Qoption CC - ‑xcomdat
    +     		+

    This version recognizes an undocumented, unsupported flag that + improves its success in compiling templates:

    -

    This flag changes the template instantiation method from - “exported” to an improved “global” - 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.

    +
    + ‑Qoption CC ‑xcomdat +
    + +

    This flag changes the template instantiation method from + “exported” to an improved “global” 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.

    +
    5.5Sun ONE Studio 8

    No current information is available. This version changes - the default template instantiation method from - “exported” (using a template repository) to - “global” (storing instances in object files - with global linkage). The linker should then automatically - detect and eliminate duplicate definitions. This change - should improve template performace over previous - releases.

    + +     		+

    No current information is available. This version changes the + default template instantiation method from “exported” + (using a template repository) to “global” (storing + instances in object files with global linkage). The linker should + then automatically detect and eliminate duplicate definitions. This + change should improve template performace over previous + releases.

    -

    Configuration Variables

    -

    The sunpro toolset responds to the following variables which can - be set in the environment or configured on the bjam command line using +

    The sunpro toolset responds to the following variables which can be set + in the environment or configured on the bjam command line using ‑sVARIABLE_NAME=value:

    -

    +

     

    + @@ -139,10 +158,10 @@ - + @@ -163,10 +182,10 @@ + property to force options such as ‑Qoption CC + ‑xcomdat into the CC command line: + “‑sSUNPRO_CXX=CC ‑Qoption CC + ‑xcomdat”. @@ -178,10 +197,7 @@ -
    Variable Name(none)Usually there is no need to set this variable at all. - However, if CC is not in the path is is usually - sufficient to configure this one variable. A typical value - for this variable is /opt/SUNWspro.Usually there is no need to set this variable at all. However, if + CC is not in the path is is usually sufficient to + configure this one variable. A typical value for this variable is + /opt/SUNWspro.
    $(SUNPRO_BIN_DIRECTORY)CC You can also use this in lieu of setting the <cxxflags> - property to force options such as ‑Qoption CC - ‑xcomdat into the CC command line: - “‑sSUNPRO_CXX=CC ‑Qoption CC - ‑xcomdat”.
     
    -

    -

    Revised diff --git a/v1/tru64cxx-tools.html b/v1/tru64cxx-tools.html index 1c36398e2..22546cc84 100644 --- a/v1/tru64cxx-tools.html +++ b/v1/tru64cxx-tools.html @@ -58,9 +58,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/vacpp-tools.html b/v1/vacpp-tools.html index c9dda9655..cc3ace02e 100644 --- a/v1/vacpp-tools.html +++ b/v1/vacpp-tools.html @@ -45,9 +45,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/variables.html b/v1/variables.html index b42fcc02d..b5d2cc1fa 100644 --- a/v1/variables.html +++ b/v1/variables.html @@ -481,9 +481,9 @@

    Copyright © Rene Rivera 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/vc7-stlport-tools.html b/v1/vc7-stlport-tools.html index 24e5b00a7..3013188fb 100644 --- a/v1/vc7-stlport-tools.html +++ b/v1/vc7-stlport-tools.html @@ -40,9 +40,10 @@ that objects build in each configuration will be built into separate directories.

    -

    Configuration Variables

    The - vc7-stlport toolset responds to the following variables, which - can be set in the environment or configured on the jam command-line using +

    Configuration + Variables

    The vc7-stlport toolset responds to the + following variables, which can be set in the environment or configured on + the jam command-line using -sVARIABLE_NAME=value. It is an extension of the msvc-stlport toolset and therefore responds to all of the MSVC -

    Toolset-Specific Features

    The following vc7 - -stlport-specific Toolset-Specific FeaturesThe + following vc7 -stlport-specific features can be used in target build requirements or in the BUILD variable: @@ -175,9 +176,9 @@

    Copyright © John Maddock 2003.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/vc7-tools.html b/v1/vc7-tools.html index c4239461c..71aff7f6c 100644 --- a/v1/vc7-tools.html +++ b/v1/vc7-tools.html @@ -72,9 +72,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/vc7.1-stlport-tools.html b/v1/vc7.1-stlport-tools.html index c97508251..a866c600b 100644 --- a/v1/vc7.1-stlport-tools.html +++ b/v1/vc7.1-stlport-tools.html @@ -40,12 +40,13 @@ multiple installed versions of STLPort, so that objects build in each configuration will be built into separate directories.

    -

    Configuration Variables

    The - vc7.1-stlport toolset responds to the following variables, - which can be set in the environment or configured on the jam command-line - using -sVARIABLE_NAME=value. It is an extension - of the msvc-stlport toolset and - therefore responds to all of the MSVC Configuration + VariablesThe vc7.1-stlport toolset responds to the + following variables, which can be set in the environment or configured on + the jam command-line using + -sVARIABLE_NAME=value. It is an extension of the + msvc-stlport toolset and therefore + responds to all of the MSVC configuration variables in addition to those listed below. @@ -112,8 +113,8 @@ -

    Toolset-Specific Features

    The following vc7 - -stlport-specific Toolset-Specific FeaturesThe + following vc7 -stlport-specific features can be used in target build requirements or in the BUILD variable: @@ -175,9 +176,9 @@

    Copyright © John Maddock 2003.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)

    diff --git a/v1/vc7.1-tools.html b/v1/vc7.1-tools.html index a7a7646ff..7f87c6881 100755 --- a/v1/vc7.1-tools.html +++ b/v1/vc7.1-tools.html @@ -73,9 +73,9 @@

    Copyright © Dave Abrahams 2002.

    -

    Use, modification, and distribution are subject to the Boost - Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at Distributed under the Boost Software License, Version 1.0. (See + accompanying file LICENSE_1_0.txt or + copy at www.boost.org/LICENSE_1_0.txt)