diff --git a/doc/configuring_boost.qbk b/doc/configuring_boost.qbk index ad391748..dc3d933e 100644 --- a/doc/configuring_boost.qbk +++ b/doc/configuring_boost.qbk @@ -61,7 +61,7 @@ user code is to monitor the discussions on the Boost developers list. [section Using the configure script] -[note +[important This configure script only sets up the Boost headers for use with a particular compiler. It has no effect on Boost.Build, or how the libraries are built. ] diff --git a/doc/html/boost_config/acknowledgements.html b/doc/html/boost_config/acknowledgements.html index e7c666fe..714c3ac0 100644 --- a/doc/html/boost_config/acknowledgements.html +++ b/doc/html/boost_config/acknowledgements.html @@ -23,7 +23,8 @@

-Acknowledgements

+Acknowledgements +

Beman Dawes provided the original config.hpp and part of this document. diff --git a/doc/html/boost_config/boost_macro_reference.html b/doc/html/boost_config/boost_macro_reference.html index fe2d8ac6..b4ef3cc7 100644 --- a/doc/html/boost_config/boost_macro_reference.html +++ b/doc/html/boost_config/boost_macro_reference.html @@ -24,7 +24,8 @@

-Boost Macro Reference

+Boost Macro Reference +
Macros that describe defects
@@ -44,7 +45,8 @@
+ that describe defects +

The following macros all describe features that are required by the C++ standard, if one of the following macros is defined, then it represents a defect in @@ -1152,7 +1154,8 @@

Macros - that describe optional features

+ that describe optional features +

The following macros describe features that are not required by the C++ standard. The macro is only defined if the feature is present. @@ -2059,7 +2062,8 @@

Macros - that describe C++0x features

+ that describe C++0x features +

The following macros describe features that are likely to be included in the upcoming ISO C++ standard, C++0x. @@ -2163,7 +2167,8 @@

Boost - Helper Macros

+ Helper Macros +

The following macros are either simple helpers, or macros that provide workarounds for compiler/standard library defects. @@ -2459,7 +2464,8 @@

Boost - Informational Macros

+ Informational Macros +

The following macros describe boost features; these are, generally speaking the only boost macros that should be tested in user code. @@ -2697,7 +2703,8 @@

Macros - for libraries with separate source code

+ for libraries with separate source code +
ABI Fixing
@@ -2713,7 +2720,8 @@
+ Fixing +

When linking against a pre-compiled library it vital that the ABI used by the compiler when building the library matches exactly @@ -2772,7 +2780,8 @@

Automatic - library selection

+ library selection +

It is essential that users link to a build of a library which was built against the same runtime library that their application will be built against diff --git a/doc/html/boost_config/guidelines_for_boost_authors.html b/doc/html/boost_config/guidelines_for_boost_authors.html index f501e709..2e433693 100644 --- a/doc/html/boost_config/guidelines_for_boost_authors.html +++ b/doc/html/boost_config/guidelines_for_boost_authors.html @@ -25,7 +25,8 @@

Guidelines for - Boost Authors

+ Boost Authors +
Adding New Defect Macros
@@ -103,7 +104,8 @@
+ New Defect Macros +

When you need to add a new defect macro -either to fix a problem with an existing library, or when adding a new library- distil the issue down to @@ -204,7 +206,8 @@

Adding - New Feature Test Macros

+ New Feature Test Macros +

When you need to add a macro that describes a feature that the standard does not require, follow the convention for adding a new defect macro (above), @@ -227,7 +230,8 @@

Modifying - the Boost Configuration Headers

+ the Boost Configuration Headers +

The aim of boost's configuration setup is that the configuration headers should be relatively stable - a boost user should not have to recompile their diff --git a/doc/html/boost_config/rationale.html b/doc/html/boost_config/rationale.html index e1c80f1d..6d37cd14 100644 --- a/doc/html/boost_config/rationale.html +++ b/doc/html/boost_config/rationale.html @@ -24,7 +24,8 @@

-Rationale

+Rationale +
The problem
The solution
@@ -40,7 +41,8 @@

Consider a situation in which you are concurrently developing on multiple platforms. Then consider adding a new platform or changing the platform definitions @@ -102,7 +104,8 @@

-The solution

+The solution +

The approach taken by boost's configuration headers is to separate configuration into three orthogonal parts: the compiler, the standard library and the platform. diff --git a/doc/html/index.html b/doc/html/index.html index d6919414..93ee53cd 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -28,7 +28,7 @@

-

+

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

@@ -91,7 +91,8 @@
+ Boost for Your Platform +
Using the default boost configuration
@@ -109,7 +110,8 @@
+ the default boost configuration +

Boost comes already configured for most common compilers and platforms; you should be able to use boost "as is". Since the compiler is configured @@ -132,7 +134,8 @@

The - <boost/config.hpp> header

+ <boost/config.hpp> header +

Boost library implementations access configuration macros via

@@ -165,22 +168,17 @@

Using - the configure script

-
+ the configure script + +
- - + + - +
[Note]Note[Important]Important
-

-

-

- This configure script only sets up the Boost headers for use with a particular - compiler. It has no effect on Boost.Build, or how the libraries are built. -

-

-

-

+ This configure script only sets up the Boost headers for use with a particular + compiler. It has no effect on Boost.Build, or how the libraries are built. +

If you know that boost is incorrectly configured for your particular setup, @@ -321,7 +319,8 @@

+ settable options +

There are some configuration-options that represent user choices, rather than compiler defects or platform specific options. These are listed in @@ -684,7 +683,8 @@

Advanced - configuration usage

+ configuration usage +
Example 1, creating our own frozen configuration
@@ -727,7 +727,8 @@
+ 1, creating our own frozen configuration +

Lets suppose that we're building boost with Visual C++ 6, and STLport 4.0. Lets suppose also that we don't intend to update our compiler or standard @@ -759,7 +760,8 @@

Example - 2: skipping files that you don't need

+ 2: skipping files that you don't need +

Lets suppose that you're using boost with a compiler that is fully conformant with the standard; you're not interested in the fact that older versions @@ -777,7 +779,8 @@

Example - 3: using configure script to freeze the boost configuration

+ 3: using configure script to freeze the boost configuration +

If you are working on a unix-like platform then you can use the configure script to generate a "frozen" configuration based on your current @@ -789,7 +792,8 @@

Testing - the boost configuration

+ the boost configuration +

The boost configuration library provides a full set of regression test programs under the <boost-root>/boost/config/ @@ -957,7 +961,7 @@

- +

Last revised: August 25, 2007 at 12:03:01 GMT

Last revised: November 01, 2007 at 18:18:14 GMT