diff --git a/getting_started/detail/common-footnotes.rst b/getting_started/detail/common-footnotes.rst index 980600b..9875f03 100644 --- a/getting_started/detail/common-footnotes.rst +++ b/getting_started/detail/common-footnotes.rst @@ -20,7 +20,3 @@ these choices don't affect binary compatibility with other compiled code, you can't count on that with Boost libraries. -.. [#native] This feature of STLPort is deprecated because it's - impossible to make it work transparently to the user; we don't - recommend it. - diff --git a/getting_started/detail/library-naming.rst b/getting_started/detail/library-naming.rst index 08da85f..6ae102c 100644 --- a/getting_started/detail/library-naming.rst +++ b/getting_started/detail/library-naming.rst @@ -6,7 +6,7 @@ In order to choose the right binary for your build configuration you need to know how Boost binaries are named. Each library filename is composed of a common sequence of elements that describe how it was built. For example, -``libboost_regex-vc71-mt-d-1_34.lib`` can be broken down into the +``libboost_regex-vc71-mt-d-x86-1_34.lib`` can be broken down into the following elements: ``lib`` @@ -51,10 +51,39 @@ following elements: For example, if you build a debug version of your code for use with debug versions of the static runtime library and the - STLPort standard library in “native iostreams” mode, - the tag would be: ``-sgdpn``. If none of the above apply, the + STLPort standard library, + the tag would be: ``-sgdp``. If none of the above apply, the ABI tag is ommitted. +``-x86`` + *Architecture and address model tag*: in the first letter, encodes the architecture as follows: + + +-----+------------------+---------------------+ + |Key |Architecture |Boost.Build option | + +=====+==================+=====================+ + |``x``|x86-32, x86-64 |architecture=x86 | + +-----+------------------+---------------------+ + |``a``|ARM |architecture=arm | + +-----+------------------+---------------------+ + |``i``|IA-64 |architecture=ia64 | + +-----+------------------+---------------------+ + |``s``|Sparc |architecture=sparc | + +-----+------------------+---------------------+ + |``m``|MIPS/SGI |architecture=mips* | + +-----+------------------+---------------------+ + |``p``|RS/6000 & PowerPC |architecture=power | + +-----+------------------+---------------------+ + + The two digits following the letter encode the address model as follows: + + +------+------------------+---------------------+ + |Key |Address model |Boost.Build option | + +======+==================+=====================+ + |``32``|32 bit |address-model=32 | + +------+------------------+---------------------+ + |``64``|64 bit |address-model=64 | + +------+------------------+---------------------+ + ``-1_34`` *Version tag*: the full Boost release number, with periods replaced by underscores. For example, version 1.31.1 would be diff --git a/getting_started/index.html b/getting_started/index.html index 73a8597..6358b39 100644 --- a/getting_started/index.html +++ b/getting_started/index.html @@ -3,7 +3,7 @@ - + Boost Getting Started diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html index a835ca5..1b2f88e 100644 --- a/getting_started/unix-variants.html +++ b/getting_started/unix-variants.html @@ -3,7 +3,7 @@ - + Boost Getting Started on Unix Variants @@ -572,7 +572,7 @@ command lines we explored earlier.

you need to know how Boost binaries are named. Each library filename is composed of a common sequence of elements that describe how it was built. For example, -libboost_regex-vc71-mt-d-1_34.lib can be broken down into the +libboost_regex-vc71-mt-d-x86-1_34.lib can be broken down into the following elements:

lib
@@ -635,10 +635,80 @@ your compiler.

For example, if you build a debug version of your code for use with debug versions of the static runtime library and the -STLPort standard library in “native iostreams” mode, -the tag would be: -sgdpn. If none of the above apply, the +STLPort standard library, +the tag would be: -sgdp. If none of the above apply, the ABI tag is ommitted.

+
-x86
+

Architecture and address model tag: in the first letter, encodes the architecture as follows:

+
+ +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
KeyArchitectureBoost.Build option
xx86-32, x86-64architecture=x86
aARMarchitecture=arm
iIA-64architecture=ia64
sSparcarchitecture=sparc
mMIPS/SGIarchitecture=mips*
pRS/6000 & PowerPCarchitecture=power
+
+

The two digits following the letter encode the address model as follows:

+
+ +++++ + + + + + + + + + + + + + + + + +
KeyAddress modelBoost.Build option
3232 bitaddress-model=32
6464 bitaddress-model=64
+
+
-1_34
Version tag: the full Boost release number, with periods replaced by underscores. For example, version 1.31.1 would be @@ -772,14 +842,6 @@ these choices don't affect binary compatibility with other compiled code, you can't count on that with Boost libraries. - - - - - -
[6]This feature of STLPort is deprecated because it's -impossible to make it work transparently to the user; we don't -recommend it.
diff --git a/getting_started/windows.html b/getting_started/windows.html index 50c136b..c2196c3 100644 --- a/getting_started/windows.html +++ b/getting_started/windows.html @@ -3,7 +3,7 @@ - + Boost Getting Started on Windows @@ -660,7 +660,7 @@ you can probably ski you need to know how Boost binaries are named. Each library filename is composed of a common sequence of elements that describe how it was built. For example, -libboost_regex-vc71-mt-d-1_34.lib can be broken down into the +libboost_regex-vc71-mt-d-x86-1_34.lib can be broken down into the following elements:

lib
@@ -723,10 +723,80 @@ your compiler.

For example, if you build a debug version of your code for use with debug versions of the static runtime library and the -STLPort standard library in “native iostreams” mode, -the tag would be: -sgdpn. If none of the above apply, the +STLPort standard library, +the tag would be: -sgdp. If none of the above apply, the ABI tag is ommitted.

+
-x86
+

Architecture and address model tag: in the first letter, encodes the architecture as follows:

+
+ +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
KeyArchitectureBoost.Build option
xx86-32, x86-64architecture=x86
aARMarchitecture=arm
iIA-64architecture=ia64
sSparcarchitecture=sparc
mMIPS/SGIarchitecture=mips*
pRS/6000 & PowerPCarchitecture=power
+
+

The two digits following the letter encode the address model as follows:

+
+ +++++ + + + + + + + + + + + + + + + + +
KeyAddress modelBoost.Build option
3232 bitaddress-model=32
6464 bitaddress-model=64
+
+
-1_34
Version tag: the full Boost release number, with periods replaced by underscores. For example, version 1.31.1 would be @@ -869,14 +939,6 @@ these choices don't affect binary compatibility with other compiled code, you can't count on that with Boost libraries. - - - - - -
[7]This feature of STLPort is deprecated because it's -impossible to make it work transparently to the user; we don't -recommend it.