diff --git a/index.html b/index.html index 9a94dcd7b..ede2affb1 100644 --- a/index.html +++ b/index.html @@ -2,18 +2,17 @@ - - + + Building Boost Libraries -

- - c++boost.gif (8819 bytes)Building -Boost Libraries

+

c++boost.gif (8819 bytes)Building Boost Libraries

Introduction
Preliminaries
@@ -21,307 +20,349 @@ Boost Libraries Configuring the tools
Supported Toolsets
Boost.Jam executable

+

Introduction

-

These instructions explain how to accomplish common tasks using -Boost.Build, the Boost Build System. The build system uses Boost.Jam, an extension of the -Perforce Jam -portable make replacement.

+

These instructions explain how to accomplish common tasks +using Boost.Build, the Boost Build System. The build +system uses Boost.Jam, an +extension of the Perforce +Jam portable make replacement.

For tasks not covered here, see the full build system documentation.

Note that many Boost libraries are implemented entirely within their headers, and so can be used without building object -libraries. Libraries that do require building object libraries first -include the Python, Regex, and Threads libraries. +libraries. Libraries that do require building object libraries +first include the Python, +Regex, Signal, and Threads libraries.

Preliminaries

+

Building Boost Libraries

-

Using your operating system's command line interpreter, execute the following -steps. The sample commands given will work for both UNIX and Windows.

+

Using your operating system's command line interpreter, +execute the following steps. The sample commands given will work +for both UNIX and Windows.

+

 

+

Configuring the tools

-

The build system's toolsets are designed to work in either of two ways:

+ +

The build system's toolsets are designed to work in either of +two ways:

+
    - -
  1. The user sets up all of the environment for each toolset he - wants to use in the normal way. For example, for Microsoft VC++, - ...vc98/bin is in the path, vcvars32.bat or equivalent has been - invoked, etc. For Metrowerks CodeWarrior, cwenv.bat or equivalent - has been called and ...Other Metrowerks Tools/Command Line Tools - is in the path. Many Unix operating systems come preconfigured - this way and require no user intervention.
    -
    - -
  2. The user doesn't want his environment cluttered with settings or - has non-standard installations for some of his tools. Instead, he - or she sets variables which point to the toolset installation - directories, either in the command shell environment or on the - bjam command-line. These variables are used by the - build system to locate the tools and invoke the necessary - setup. +
  3. The user sets up all of the environment for each toolset + he wants to use in the normal way. For example, for + Microsoft VC++, ...vc98/bin is in the path, vcvars32.bat + or equivalent has been invoked, etc. For Metrowerks + CodeWarrior, cwenv.bat or equivalent has been called and + ...Other Metrowerks Tools/Command Line Tools is in the + path. Many Unix operating systems come preconfigured this + way and require no user intervention.
    +
    +
    4. +
  4. The user doesn't want his environment cluttered with + settings or has non-standard installations for some of + his tools. Instead, he or she sets variables which point + to the toolset installation directories, either in the + command shell environment or on the bjam + command-line. These variables are used by the build + system to locate the tools and invoke the necessary setup. +

Supported Toolsets

-The following toolsets are supported by Boost.Build. For information - about configuring each toolset, click its name in the leftmost - column. +

The following toolsets are supported by Boost.Build. For +information about configuring each +toolset, click its name in the leftmost column.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TOOLS NameDescription
borlandBorland C++
comoComeau C++ compiler front-end for Windows, - using Microsoft Visual C++as a back-end.
gccGNU GCC on Unix and Cygwin.
gcc-stlportGNU GCC on Unix and Cygwin, using the STLport standard library - implementation
gcc-nocygwinGNU GCC Cygwin command line compiler tools running in - "no-cygwin" mode, using the STLport - standard library implementation (produces commercially redistributable - objects)
intel-win32Intel - C++ for Windows using the Dinkumware standard library in the Intel-required Microsoft - Visual C++ 6 or 7 - installation
intel-linuxIntel C++ for Linux
kccKAI C++
metrowerksMetrowerks CodeWarrior command-line tools
mingwGNU GCC and associated tools in MinGW configuration (produces - commercially redistributable objects)
mipsproSGI - MIPSpro C and C++
mipsproSGI - MIPSpro C and C++
msvcMicrosoft Visual - C++ command-line tools.
msvc-stlportMicrosoft Visual - C++ command-line tools, using the STLport standard library - implementation
tru64cxxCompaq C++ - for Tru64 UNIX (versions prior to 6.5)
tru64cxx65Compaq C++ - Version 6.5 for Tru64 UNIX
vacppIBM Visual - Age C++ command-line tools
vc7Microsoft Visual - C++ command-line tools, in case you are using the msvc toolset for a Visual - C++ 6.x.
TOOLS NameDescription
borlandBorland + C++
comoComeau C++ + compiler front-end for Windows, using Microsoft Visual C++as + a back-end.
gccGNU GCC on Unix and Cygwin.
gcc-stlportGNU GCC on Unix and Cygwin, using the STLport standard + library implementation
gcc-nocygwinGNU GCC Cygwin command line compiler tools running in + "no-cygwin" mode, using the STLport standard + library implementation (produces commercially + redistributable objects)
intel-win32Intel + C++ for Windows using the Dinkumware standard library + in the Intel-required Microsoft Visual C++ + 6 or 7 installation
intel-linuxIntel + C++ for Linux
kccKAI + C++
metrowerksMetrowerks + CodeWarrior command-line tools
mingwGNU GCC and associated tools in MinGW configuration (produces + commercially redistributable objects)
mipsproSGI MIPSpro + C and C++
mipsproSGI MIPSpro + C and C++
msvcMicrosoft Visual C++ + command-line tools.
msvc-stlportMicrosoft Visual C++ + command-line tools, using the STLport standard + library implementation
tru64cxxCompaq + C++ for Tru64 UNIX (versions prior to 6.5)
tru64cxx65Compaq + C++ Version 6.5 for Tru64 UNIX
vacppIBM + Visual Age C++ command-line tools
vc7Microsoft Visual C++ + command-line tools, in case you are using the msvc toolset for + a Visual + C++ 6.x.
-

Unless otherwise specified, the library is assumed to be the one shipped with -the compiler.

-

Additional tools can be supplied by adding an appropriate xxxx-tools.jam file -to the tools/build subdirectory, where xxxx is the name of the tool being -added. If you write an additional toolset file, please submit it to Boost -so others may benefit from your work.

+

Unless otherwise specified, the library is assumed to be the +one shipped with the compiler.

+ +

Additional tools can be supplied by adding an appropriate xxxx-tools.jam +file to the tools/build subdirectory, where xxxx is the name of +the tool being added. If you write an additional toolset file, +please submit it to Boost so others may benefit from your work.

Boost.Jam executable

-

Pre-built Boost.Jam executables are available for the following platforms:

- - -

RedHat Linux RPM packages are available:

-

The Boost.Jam source files are included in the Boost distribution, so you can build -the Boost.Jam executable yourself:

- -
-

Revised 24 May, 2002 -

-

© Copyright 2001 Beman Dawes

+ +

Revised 20 July, 2002

+ +

© Copyright 2001 Beman Dawes

+

 

- - - \ No newline at end of file + diff --git a/v1/index.html b/v1/index.html index 9a94dcd7b..ede2affb1 100644 --- a/v1/index.html +++ b/v1/index.html @@ -2,18 +2,17 @@ - - + + Building Boost Libraries -

- - c++boost.gif (8819 bytes)Building -Boost Libraries

+

c++boost.gif (8819 bytes)Building Boost Libraries

Introduction
Preliminaries
@@ -21,307 +20,349 @@ Boost Libraries Configuring the tools
Supported Toolsets
Boost.Jam executable

+

Introduction

-

These instructions explain how to accomplish common tasks using -Boost.Build, the Boost Build System. The build system uses Boost.Jam, an extension of the -Perforce Jam -portable make replacement.

+

These instructions explain how to accomplish common tasks +using Boost.Build, the Boost Build System. The build +system uses Boost.Jam, an +extension of the Perforce +Jam portable make replacement.

For tasks not covered here, see the full build system documentation.

Note that many Boost libraries are implemented entirely within their headers, and so can be used without building object -libraries. Libraries that do require building object libraries first -include the Python, Regex, and Threads libraries. +libraries. Libraries that do require building object libraries +first include the Python, +Regex, Signal, and Threads libraries.

Preliminaries

+

Building Boost Libraries

-

Using your operating system's command line interpreter, execute the following -steps. The sample commands given will work for both UNIX and Windows.

+

Using your operating system's command line interpreter, +execute the following steps. The sample commands given will work +for both UNIX and Windows.

+

 

+

Configuring the tools

-

The build system's toolsets are designed to work in either of two ways:

+ +

The build system's toolsets are designed to work in either of +two ways:

+
    - -
  1. The user sets up all of the environment for each toolset he - wants to use in the normal way. For example, for Microsoft VC++, - ...vc98/bin is in the path, vcvars32.bat or equivalent has been - invoked, etc. For Metrowerks CodeWarrior, cwenv.bat or equivalent - has been called and ...Other Metrowerks Tools/Command Line Tools - is in the path. Many Unix operating systems come preconfigured - this way and require no user intervention.
    -
    - -
  2. The user doesn't want his environment cluttered with settings or - has non-standard installations for some of his tools. Instead, he - or she sets variables which point to the toolset installation - directories, either in the command shell environment or on the - bjam command-line. These variables are used by the - build system to locate the tools and invoke the necessary - setup. +
  3. The user sets up all of the environment for each toolset + he wants to use in the normal way. For example, for + Microsoft VC++, ...vc98/bin is in the path, vcvars32.bat + or equivalent has been invoked, etc. For Metrowerks + CodeWarrior, cwenv.bat or equivalent has been called and + ...Other Metrowerks Tools/Command Line Tools is in the + path. Many Unix operating systems come preconfigured this + way and require no user intervention.
    +
    +
    4. +
  4. The user doesn't want his environment cluttered with + settings or has non-standard installations for some of + his tools. Instead, he or she sets variables which point + to the toolset installation directories, either in the + command shell environment or on the bjam + command-line. These variables are used by the build + system to locate the tools and invoke the necessary setup. +

Supported Toolsets

-The following toolsets are supported by Boost.Build. For information - about configuring each toolset, click its name in the leftmost - column. +

The following toolsets are supported by Boost.Build. For +information about configuring each +toolset, click its name in the leftmost column.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TOOLS NameDescription
borlandBorland C++
comoComeau C++ compiler front-end for Windows, - using Microsoft Visual C++as a back-end.
gccGNU GCC on Unix and Cygwin.
gcc-stlportGNU GCC on Unix and Cygwin, using the STLport standard library - implementation
gcc-nocygwinGNU GCC Cygwin command line compiler tools running in - "no-cygwin" mode, using the STLport - standard library implementation (produces commercially redistributable - objects)
intel-win32Intel - C++ for Windows using the Dinkumware standard library in the Intel-required Microsoft - Visual C++ 6 or 7 - installation
intel-linuxIntel C++ for Linux
kccKAI C++
metrowerksMetrowerks CodeWarrior command-line tools
mingwGNU GCC and associated tools in MinGW configuration (produces - commercially redistributable objects)
mipsproSGI - MIPSpro C and C++
mipsproSGI - MIPSpro C and C++
msvcMicrosoft Visual - C++ command-line tools.
msvc-stlportMicrosoft Visual - C++ command-line tools, using the STLport standard library - implementation
tru64cxxCompaq C++ - for Tru64 UNIX (versions prior to 6.5)
tru64cxx65Compaq C++ - Version 6.5 for Tru64 UNIX
vacppIBM Visual - Age C++ command-line tools
vc7Microsoft Visual - C++ command-line tools, in case you are using the msvc toolset for a Visual - C++ 6.x.
TOOLS NameDescription
borlandBorland + C++
comoComeau C++ + compiler front-end for Windows, using Microsoft Visual C++as + a back-end.
gccGNU GCC on Unix and Cygwin.
gcc-stlportGNU GCC on Unix and Cygwin, using the STLport standard + library implementation
gcc-nocygwinGNU GCC Cygwin command line compiler tools running in + "no-cygwin" mode, using the STLport standard + library implementation (produces commercially + redistributable objects)
intel-win32Intel + C++ for Windows using the Dinkumware standard library + in the Intel-required Microsoft Visual C++ + 6 or 7 installation
intel-linuxIntel + C++ for Linux
kccKAI + C++
metrowerksMetrowerks + CodeWarrior command-line tools
mingwGNU GCC and associated tools in MinGW configuration (produces + commercially redistributable objects)
mipsproSGI MIPSpro + C and C++
mipsproSGI MIPSpro + C and C++
msvcMicrosoft Visual C++ + command-line tools.
msvc-stlportMicrosoft Visual C++ + command-line tools, using the STLport standard + library implementation
tru64cxxCompaq + C++ for Tru64 UNIX (versions prior to 6.5)
tru64cxx65Compaq + C++ Version 6.5 for Tru64 UNIX
vacppIBM + Visual Age C++ command-line tools
vc7Microsoft Visual C++ + command-line tools, in case you are using the msvc toolset for + a Visual + C++ 6.x.
-

Unless otherwise specified, the library is assumed to be the one shipped with -the compiler.

-

Additional tools can be supplied by adding an appropriate xxxx-tools.jam file -to the tools/build subdirectory, where xxxx is the name of the tool being -added. If you write an additional toolset file, please submit it to Boost -so others may benefit from your work.

+

Unless otherwise specified, the library is assumed to be the +one shipped with the compiler.

+ +

Additional tools can be supplied by adding an appropriate xxxx-tools.jam +file to the tools/build subdirectory, where xxxx is the name of +the tool being added. If you write an additional toolset file, +please submit it to Boost so others may benefit from your work.

Boost.Jam executable

-

Pre-built Boost.Jam executables are available for the following platforms:

- - -

RedHat Linux RPM packages are available:

-

The Boost.Jam source files are included in the Boost distribution, so you can build -the Boost.Jam executable yourself:

- -
-

Revised 24 May, 2002 -

-

© Copyright 2001 Beman Dawes

+ +

Revised 20 July, 2002

+ +

© Copyright 2001 Beman Dawes

+

 

- - - \ No newline at end of file +