Getting Started
+
+
@@ -52,6 +58,7 @@ your actual name.
Ready?
Let's go!
Getting StartedLet's go!
Getting Started on Unix VariantsThe most reliable way to get a copy of Boost is to download a distribution from SourceForge:
Download boost_1_44_0.tar.bz2.
+Download boost_1_44_0.tar.bz2.
In the directory where you want to put the Boost installation, execute
-tar --bzip2 -xf /path/to/boost_1_44_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_44_0.tar.bz2
Some older libraries and most very small libraries place all -public headers directly into boost/.
+public headers directly into boost/.Most libraries' public headers live in a subdirectory of -boost/, named after the library. For example, you'll find -the Python library's def.hpp header in
+boost/, named after the library. For example, you'll find +the Python library's def.hpp header in-boost/python/def.hpp. +boost/python/def.hpp.
Some libraries have an “aggregate header” in boost/ that -#includes all of the library's other headers. For +
Some libraries have an “aggregate header” in boost/ that +#includes all of the library's other headers. For example, Boost.Python's aggregate header is
-boost/python.hpp. +boost/python.hpp.
Most libraries place private headers in a subdirectory called -detail/, or aux_/. Don't expect to find +detail/, or aux_/. Don't expect to find anything you can use in these directories.
It's important to note the following:
The path to the boost root directory (often /usr/local/boost_1_44_0) is -sometimes referred to as $BOOST_ROOT in documentation and +
The path to the boost root directory (often /usr/local/boost_1_44_0) is +sometimes referred to as $BOOST_ROOT in documentation and mailing lists .
To compile anything in Boost, you need a directory containing -the boost/ subdirectory in your #include path.
+the boost/ subdirectory in your #include path.Since all of Boost's header files have the .hpp extension, -and live in the boost/ subdirectory of the boost root, your -Boost #include directives will look like:
+Since all of Boost's header files have the .hpp extension, +and live in the boost/ subdirectory of the boost root, your +Boost #include directives will look like:
#include <boost/whatever.hpp>@@ -156,9 +162,9 @@ Boost #include direct
depending on your preference regarding the use of angle bracket includes.
Don't be distracted by the doc/ subdirectory; it only +
Don't be distracted by the doc/ subdirectory; it only contains a subset of the Boost documentation. Start with -libs/index.html if you're looking for the whole enchilada.
+libs/index.html if you're looking for the whole enchilada.A few libraries have optional separately-compiled binaries:
Copy the text of this program into a file called example.cpp.
-Now, in the directory where you saved example.cpp, issue the +
Copy the text of this program into a file called example.cpp.
+Now, in the directory where you saved example.cpp, issue the following command:
-c++ -I path/to/boost_1_44_0 example.cpp -o example
+c++ -I path/to/boost_1_44_0 example.cpp -o example
To test the result, type:
@@ -259,29 +265,29 @@ correctly identified the5.1 Easy Build and Install
-Issue the following commands in the shell (don't type $; that +
Issue the following commands in the shell (don't type $; that represents the shell's prompt):
-$ cd path/to/boost_1_44_0 +$ cd path/to/boost_1_44_0 $ ./bootstrap.sh --help-Select your configuration options and invoke ./bootstrap.sh again +
Select your configuration options and invoke ./bootstrap.sh again without the --help option. Unless you have write permission in -your system's /usr/local/ directory, you'll probably want to at +your system's /usr/local/ directory, you'll probably want to at least use
$ ./bootstrap.sh --prefix=path/to/installation/prefixto install somewhere else. Also, consider using the ---show-libraries and --with-libraries=library_name_list options to limit the +--show-libraries and --with-libraries=library-name-list options to limit the long wait you'll experience if you build everything. Finally,
$ ./bjam install-will leave Boost binaries in the lib/ subdirectory of your +
will leave Boost binaries in the lib/ subdirectory of your installation prefix. You will also find a copy of the Boost -headers in the include/ subdirectory of the installation -prefix, so you can henceforth use that directory as an #include +headers in the include/ subdirectory of the installation +prefix, so you can henceforth use that directory as an #include path in place of the Boost root directory.
@@ -302,19 +308,19 @@ separately. See the Boost.Build is a text-based system for developing, testing, and installing software. To use it, you'll need an executable called -bjam. +bjam.-5.2.1 Get bjam
-bjam is the command-line tool that drives the Boost Build -system. To build Boost binaries, you'll invoke bjam from the +
5.2.1 Get bjam
+bjam is the command-line tool that drives the Boost Build +system. To build Boost binaries, you'll invoke bjam from the Boost root.
-We suggest you download a pre-built bjam executable for your platform. -Alternatively, you can build bjam yourself using these +
We suggest you download a pre-built bjam executable for your platform. +Alternatively, you can build bjam yourself using these instructions.
-Move the bjam executable into a directory in your PATH. You can +
Move the bjam executable into a directory in your PATH. You can see the list of directories in your PATH, separated by colons, -by typing “echo $PATH” at the command prompt.
+by typing “echo $PATH” at the command prompt.5.2.2 Identify Your Toolset
@@ -341,70 +347,70 @@ Name -acc +- acc Hewlett Packard Only very recent versions are known to work well with Boost borland +- borland Borland como +- como Comeau Computing Using this toolset may require configuring another toolset to act as its backend cw +- cw Metrowerks/Freescale The CodeWarrior compiler. We have not tested versions of this compiler produced since it was sold to Freescale. dmc +- dmc Digital Mars As of this Boost release, no version of dmc is known to handle Boost well. darwin +- darwin Apple Computer Apple's version of the GCC toolchain with support for Darwin and MacOS X features such as frameworks. gcc +- gcc The Gnu Project Includes support for Cygwin and MinGW compilers. hp_cxx +- hp_cxx Hewlett Packard Targeted at the Tru64 operating system. intel +- intel Intel msvc +- msvc Microsoft qcc +- qcc QNX Software Systems sun +- sun Sun Only very recent versions are known to work well with Boost. vacpp +@@ -420,13 +426,13 @@ a hyphen, e.g. intel-9.0Boost.Build will place all intermediate files it generates while building into the build directory. If your Boost root directory is writable, this step isn't strictly necessary: by -default Boost.Build will create a bin.v2/ subdirectory for that +default Boost.Build will create a bin.v2/ subdirectory for that purpose in your current working directory. vacpp IBM The VisualAge C++ compiler. -@@ -549,21 +555,21 @@ project.5.2.4 Invoke bjam
+5.2.4 Invoke bjam
Change your current directory to the Boost root directory and -invoke bjam as follows:
+invoke bjam as follows:bjam --build-dir=build-directory toolset=toolset-name stage@@ -434,23 +440,23 @@ bjam --build-dir=Boost.Build documentation.For example, your session might look like this:
-$ cd ~/boost_1_44_0 +$ cd ~/boost_1_44_0 $ bjam --build-dir=/tmp/build-boost toolset=gcc stageThat will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “--build-type=complete”.
-Building the special stage target places Boost -library binaries in the stage/lib/ subdirectory of your build +
Building the special stage target places Boost +library binaries in the stage/lib/ subdirectory of your build directory.
Note
-bjam is case-sensitive; it is important that all the +
bjam is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.
For a description of other options you can pass when invoking -bjam, type:
+bjam, type:bjam --help@@ -458,16 +464,16 @@ bjam --help be interested in:
- reviewing the list of library names with --show-libraries
-- limiting which libraries get built with the --with-libraries=library-name-list option
-- choosing a specific build variant by adding release or -debug to the command line.
+- limiting which libraries get built with the --with-library-name or --without-library-name options
+- choosing a specific build variant by adding release or +debug to the command line.
Note
Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure everything is went well, you might redirect the output into a -file by appending “>build.log 2>&1” to your command line.
+file by appending “>build.log 2>&1” to your command line.
- -
You can specify the full path to each library:
-$ c++ -I path/to/boost_1_44_0 example.cpp -o example \ +$ c++ -I path/to/boost_1_44_0 example.cpp -o example \ ~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.aYou can separately specify a directory to search (with -Ldirectory) and a library name to search for (with -llibrary,2 dropping the filename's leading lib and trailing -suffix (.a in this case):
+- @@ -582,13 +588,13 @@ how it was built. For example, libboost_regex-vc71-mt-d-1_34.lib can be broken down into the following elements:
You can separately specify a directory to search (with -Ldirectory) and a library name to search for (with -llibrary,2 dropping the filename's leading lib and trailing +suffix (.a in this case):
-$ c++ -I path/to/boost_1_44_0 example.cpp -o example \ +$ c++ -I path/to/boost_1_44_0 example.cpp -o example \ -L~/boost/stage/lib/ -lboost_regex-gcc34-mt-d-1_36As you can see, this method is just as terse as method A for one library; it really pays off when you're using multiple libraries from the same directory. Note, however, that if you -use this method with a library that has both static (.a) and -dynamic (.so) builds, the system may choose one +use this method with a library that has both static (.a) and +dynamic (.so) builds, the system may choose one automatically for you unless you pass a special option such as -static on the command line.
-
- lib
+- lib
- Prefix: except on Microsoft Windows, every Boost library name begins with this string. On Windows, only ordinary static -libraries use the lib prefix; import libraries and DLLs do +libraries use the lib prefix; import libraries and DLLs do not.4
-- boost_regex
-- Library name: all boost library filenames begin with boost_.
+- boost_regex
+- Library name: all boost library filenames begin with boost_.
- -vc71
- Toolset tag: identifies the toolset and version used to build the binary.
@@ -615,24 +621,24 @@ feature, a single letter is added to the tag: -s +- s linking statically to the C++ standard library and compiler runtime support libraries. runtime-link=static g +- g using debug versions of the standard and runtime support libraries. runtime-debugging=on y +- y using a special debug build of Python. python-debugging=on d +- d building a debug version of your code.5 variant=debug p +p using the STLPort standard library rather than the default one supplied with your compiler. stdlib=stlport @@ -650,12 +656,12 @@ ABI tag is ommitted.- Version tag: the full Boost release number, with periods replaced by underscores. For example, version 1.31.1 would be tagged as "-1_31_1".
-- .lib
+- .lib
- Extension: determined according to the operating system's usual convention. On most unix-style platforms the extensions are -.a and .so for static libraries (archives) and shared -libraries, respectively. On Windows, .dll indicates a shared -library and .lib indicates a +.a and .so for static libraries (archives) and shared +libraries, respectively. On Windows, .dll indicates a shared +library and .lib indicates a static or import library. Where supported by toolsets on unix variants, a full version extension is added (e.g. ".so.1.34") and a symbolic link to the library file, named without the trailing @@ -669,7 +675,7 @@ version number, will also be created.
6.2 Test Your Program
To test our subject extraction, we'll filter the following text -file. Copy it out of your browser and save it as jayne.txt:
+file. Copy it out of your browser and save it as jayne.txt:To: George Shmidlap From: Rita Marlowe @@ -682,15 +688,15 @@ platform-specific settings so that the system will be able to find and load it when your program is run. Most platforms have an environment variable to which you can add the directory containing the library. On many platforms (Linux, FreeBSD) that variable is -LD_LIBRARY_PATH, but on MacOS it's DYLD_LIBRARY_PATH, and -on Cygwin it's simply PATH. In most shells other than csh -and tcsh, you can adjust the variable as follows (again, don't -type the $—that represents the shell prompt): +LD_LIBRARY_PATH, but on MacOS it's DYLD_LIBRARY_PATH, and +on Cygwin it's simply PATH. In most shells other than csh +and tcsh, you can adjust the variable as follows (again, don't +type the $—that represents the shell prompt):$ VARIABLE_NAME=path/to/lib/directory:${VARIABLE_NAME} $ export VARIABLE_NAME-On csh and tcsh, it's
+On csh and tcsh, it's
$ setenv VARIABLE_NAME path/to/lib/directory:${VARIABLE_NAME}@@ -776,7 +782,7 @@ same name.@@ -804,6 +810,8 @@ recommend it. + + diff --git a/more/getting_started/unix-variants.rst b/more/getting_started/unix-variants.rst index fcd919f6eb..e80378884c 100644 --- a/more/getting_started/unix-variants.rst +++ b/more/getting_started/unix-variants.rst @@ -108,7 +108,7 @@ least use **$** ./bootstrap.sh **--prefix=**\ *path*\ /\ *to*\ /\ *installation*\ /\ *prefix* to install somewhere else. Also, consider using the -``--show-libraries`` and ``--with-libraries=``\ *library_name_list* options to limit the +``--show-libraries`` and ``--with-libraries=``\ *library-name-list* options to limit the long wait you'll experience if you build everything. Finally, .. parsed-literal:: diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html index b39b04b48d..e983e88224 100644 --- a/more/getting_started/windows.html +++ b/more/getting_started/windows.html @@ -2,15 +2,21 @@ + - + [5] These libraries were compiled without optimization or inlining, with full debug symbols enabled, and without -NDEBUG #defined. Although it's true that sometimes +NDEBUG #defined. Although it's true that sometimes these choices don't affect binary compatibility with other compiled code, you can't count on that with Boost libraries. Boost Getting Started on Windows + +++ + @@ -39,10 +45,10 @@ not supported—they may or may not work.
- 5.1 Install Visual Studio Binaries
- 5.2 Or, Simplified Build From Source
- 5.3 Or, Build Binaries From Source
- 5.4 Expected Build Output
@@ -73,7 +79,7 @@ least install the Static Multithreaded variants of the boost_1_44_0.7z or boost_1_44_0.zip and unpack it to install a complete Boost +download boost_1_44_0.7z or boost_1_44_0.zip and unpack it to install a complete Boost distribution.1 @@ -104,43 +110,43 @@ distribution.1 but most libraries follow a few patterns:
Some older libraries and most very small libraries place all -public headers directly into boost\.
+public headers directly into boost\.- -
Most libraries' public headers live in a subdirectory of -boost\, named after the library. For example, you'll find -the Python library's def.hpp header in
+boost\, named after the library. For example, you'll find +the Python library's def.hpp header in-boost\python\def.hpp. +boost\python\def.hpp.Some libraries have an “aggregate header” in boost\ that -#includes all of the library's other headers. For +
Some libraries have an “aggregate header” in boost\ that +#includes all of the library's other headers. For example, Boost.Python's aggregate header is
-boost\python.hpp. +boost\python.hpp.Most libraries place private headers in a subdirectory called -detail\, or aux_\. Don't expect to find +detail\, or aux_\. Don't expect to find anything you can use in these directories.
It's important to note the following:
-
@@ -191,7 +197,7 @@ before building and installing it)The path to the boost root directory (often C:\Program Files\boost\boost_1_44_0) is -sometimes referred to as $BOOST_ROOT in documentation and +
The path to the boost root directory (often C:\Program Files\boost\boost_1_44_0) is +sometimes referred to as $BOOST_ROOT in documentation and mailing lists .
- -
To compile anything in Boost, you need a directory containing -the boost\ subdirectory in your #include path. Specific steps for setting up #include +the boost\ subdirectory in your #include path. Specific steps for setting up #include paths in Microsoft Visual Studio follow later in this document; if you use another IDE, please consult your product's documentation for instructions.
Since all of Boost's header files have the .hpp extension, -and live in the boost\ subdirectory of the boost root, your -Boost #include directives will look like:
+- -
Since all of Boost's header files have the .hpp extension, +and live in the boost\ subdirectory of the boost root, your +Boost #include directives will look like:
#include <boost/whatever.hpp>@@ -151,11 +157,11 @@ Boost #include directdepending on your preference regarding the use of angle bracket includes. Even Windows users can (and, for portability reasons, probably should) use forward slashes in -#include directives; your compiler doesn't care.
+#include directives; your compiler doesn't care.Don't be distracted by the doc\ subdirectory; it only +
Don't be distracted by the doc\ subdirectory; it only contains a subset of the Boost documentation. Start with -libs\index.html if you're looking for the whole enchilada.
+libs\index.html if you're looking for the whole enchilada.A few libraries have optional separately-compiled binaries:
- Boost.DateTime has a binary component that is only needed if -you're using its to_string/from_string or serialization +you're using its to_string/from_string or serialization features, or if you're targeting Visual C++ 6.x or Borland.
- Boost.Graph also has a binary component that is only needed if you intend to parse GraphViz files.
@@ -224,7 +230,7 @@ int main() in(std::cin), in(), std::cout << (_1 * 3) << " " ); } -Copy the text of this program into a file called example.cpp.
+Copy the text of this program into a file called example.cpp.
Note
To build the examples in this guide, you can use an @@ -253,10 +259,10 @@ cd path\to\some\directory
followed by Return. For example,
-cd C:\Program Files\boost\boost_1_44_0 +cd C:\Program Files\boost\boost_1_44_0Long commands can be continued across several lines by typing a -caret (^) at the end of all but the last line. Some examples +caret (^) at the end of all but the last line. Some examples on this page use that technique to save horizontal space.
@@ -278,14 +284,14 @@ select Properties from the resulting pop-up menuIn Configuration Properties > C/C++ > General > Additional Include Directories, enter the path to the Boost root directory, for example
-C:\Program Files\boost\boost_1_44_0
+C:\Program Files\boost\boost_1_44_0
- -
In Configuration Properties > C/C++ > Precompiled Headers, change Use Precompiled Header (/Yu) to Not Using Precompiled Headers.3
Replace the contents of the example.cpp generated by the IDE +
Replace the contents of the example.cpp generated by the IDE with the example code above.
From the Build menu, select Build Solution.
@@ -316,7 +322,7 @@ Visual Studio compiler. In that window, set the to a suitable location for creating some temporary files and type the following command followed by the Return key:-cl /EHsc /I path\to\boost_1_44_0 path\to\example.cpp +cl /EHsc /I path\to\boost_1_44_0 path\to\example.cppTo test the result, type:
@@ -346,8 +352,8 @@ you'll need to acquire library binaries.5.1 Install Visual Studio Binaries
The installers supplied by BoostPro Computing will download and -install pre-compiled binaries into the lib\ subdirectory of the -boost root, typically C:\Program Files\boost\boost_1_44_0\lib\. If you installed +install pre-compiled binaries into the lib\ subdirectory of the +boost root, typically C:\Program Files\boost\boost_1_44_0\lib\. If you installed all variants of the Boost.Regex binary, you're done with this step. Otherwise, please run the installer again and install them now.
@@ -366,7 +372,7 @@ bootstrapThe first command prepares the Boost.Build system for use. The second command invokes Boost.Build to build the separately-compiled Boost libraries. Please consult the Boost.Build documentation for a list -of options that can be passed to bjam.
+of options that can be passed to bjam.5.3 Or, Build Binaries From Source
@@ -383,19 +389,19 @@ separately. See the Boost.Build is a text-based system for developing, testing, and installing software. To use it, you'll need an executable called -bjam. +bjam.-5.3.1 Get bjam
-bjam is the command-line tool that drives the Boost Build -system. To build Boost binaries, you'll invoke bjam from the +
5.3.1 Get bjam
+bjam is the command-line tool that drives the Boost Build +system. To build Boost binaries, you'll invoke bjam from the Boost root.
-We suggest you download a pre-built bjam executable for your platform. -Alternatively, you can build bjam yourself using these +
We suggest you download a pre-built bjam executable for your platform. +Alternatively, you can build bjam yourself using these instructions.
-Move the bjam executable into a directory in your PATH. You can +
Move the bjam executable into a directory in your PATH. You can see the list of directories in your PATH, separated by semicolons, -by typing “PATH” at the command prompt.
+by typing “PATH” at the command prompt.5.3.2 Identify Your Toolset
@@ -422,70 +428,70 @@ Name -acc +- acc Hewlett Packard Only very recent versions are known to work well with Boost borland +- borland Borland como +- como Comeau Computing Using this toolset may require configuring another toolset to act as its backend cw +- cw Metrowerks/Freescale The CodeWarrior compiler. We have not tested versions of this compiler produced since it was sold to Freescale. dmc +- dmc Digital Mars As of this Boost release, no version of dmc is known to handle Boost well. darwin +- darwin Apple Computer Apple's version of the GCC toolchain with support for Darwin and MacOS X features such as frameworks. gcc +- gcc The Gnu Project Includes support for Cygwin and MinGW compilers. hp_cxx +- hp_cxx Hewlett Packard Targeted at the Tru64 operating system. intel +- intel Intel msvc +- msvc Microsoft qcc +- qcc QNX Software Systems sun +- sun Sun Only very recent versions are known to work well with Boost. vacpp +@@ -504,13 +510,13 @@ detection code) or auto-linki vacpp IBM The VisualAge C++ compiler. Boost.Build will place all intermediate files it generates while building into the build directory. If your Boost root directory is writable, this step isn't strictly necessary: by -default Boost.Build will create a bin.v2/ subdirectory for that +default Boost.Build will create a bin.v2/ subdirectory for that purpose in your current working directory.
-@@ -657,7 +663,7 @@ earlier: select Properties from the resulting pop-up menu5.3.4 Invoke bjam
+5.3.4 Invoke bjam
Change your current directory to the Boost root directory and -invoke bjam as follows:
+invoke bjam as follows:bjam --build-dir=build-directory toolset=toolset-name --build-type=complete stage@@ -518,30 +524,30 @@ bjam --build-dir=Boost.Build documentation.For example, your session might look like this:4
-C:\WINDOWS> cd C:\Program Files\boost\boost_1_44_0 -C:\Program Files\boost\boost_1_44_0> bjam ^ +C:\WINDOWS> cd C:\Program Files\boost\boost_1_44_0 +C:\Program Files\boost\boost_1_44_0> bjam ^ More? --build-dir="C:\Documents and Settings\dave\build-boost" ^ More? --build-type=complete msvc stage-Be sure to read this note about the appearance of ^, -More? and quotation marks (") in that line.
-The option “--build-type=complete” causes bjam to build +
Be sure to read this note about the appearance of ^, +More? and quotation marks (") in that line.
+The option “--build-type=complete” causes bjam to build all supported variants of the libraries. For instructions on how to build only specific variants, please ask on the Boost.Build mailing list.
-Building the special stage target places Boost -library binaries in the stage\lib\ subdirectory of your build +
Building the special stage target places Boost +library binaries in the stage\lib\ subdirectory of your build directory.
Note
-bjam is case-sensitive; it is important that all the +
bjam is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.
For a description of other options you can pass when invoking -bjam, type:
+bjam, type:bjam --help@@ -549,16 +555,16 @@ bjam --help be interested in:
- reviewing the list of library names with --show-libraries
-- limiting which libraries get built with the --with-libraries=library-name-list option
-- choosing a specific build variant by adding release or -debug to the command line.
+- limiting which libraries get built with the --with-library-name or --without-library-name options
+- choosing a specific build variant by adding release or +debug to the command line.
Note
Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure everything is went well, you might redirect the output into a -file by appending “>build.log 2>&1” to your command line.
+file by appending “>build.log 2>&1” to your command line.- In Configuration Properties > Linker > Additional Library Directories, enter the path to the Boost binaries, -e.g. C:\Program Files\boost\boost_1_44_0\lib\.
+e.g. C:\Program Files\boost\boost_1_44_0\lib\.- From the Build menu, select Build Solution.
@@ -667,9 +673,9 @@ e.g. C:\Program For example, we can compile and link the above program from the Visual C++ command-line by simply adding the bold text below to the command line we used earlier, assuming your Boost binaries are -in C:\Program Files\boost\boost_1_44_0\lib: +in C:\Program Files\boost\boost_1_44_0\lib:-cl /EHsc /I path\to\boost_1_44_0 example.cpp ^ +cl /EHsc /I path\to\boost_1_44_0 example.cpp ^ /link /LIBPATH: C:\Program Files\boost\boost_1_44_0\lib@@ -692,13 +698,13 @@ how it was built. For example, libboost_regex-vc71-mt-d-1_34.lib can be broken down into the following elements:-
- lib
+- lib
- Prefix: except on Microsoft Windows, every Boost library name begins with this string. On Windows, only ordinary static -libraries use the lib prefix; import libraries and DLLs do +libraries use the lib prefix; import libraries and DLLs do not.6
-- boost_regex
-- Library name: all boost library filenames begin with boost_.
+- boost_regex
+- Library name: all boost library filenames begin with boost_.
- -vc71
- Toolset tag: identifies the toolset and version used to build the binary.
@@ -725,24 +731,24 @@ feature, a single letter is added to the tag: -s +- s linking statically to the C++ standard library and compiler runtime support libraries. runtime-link=static g +- g using debug versions of the standard and runtime support libraries. runtime-debugging=on y +- y using a special debug build of Python. python-debugging=on d +- d building a debug version of your code.7 variant=debug p +p using the STLPort standard library rather than the default one supplied with your compiler. stdlib=stlport @@ -760,12 +766,12 @@ ABI tag is ommitted.- Version tag: the full Boost release number, with periods replaced by underscores. For example, version 1.31.1 would be tagged as "-1_31_1".
-- .lib
+- .lib
- Extension: determined according to the operating system's usual convention. On most unix-style platforms the extensions are -.a and .so for static libraries (archives) and shared -libraries, respectively. On Windows, .dll indicates a shared -library and .lib indicates a +.a and .so for static libraries (archives) and shared +libraries, respectively. On Windows, .dll indicates a shared +library and .lib indicates a static or import library. Where supported by toolsets on unix variants, a full version extension is added (e.g. ".so.1.34") and a symbolic link to the library file, named without the trailing @@ -779,7 +785,7 @@ version number, will also be created.
6.4 Test Your Program
To test our subject extraction, we'll filter the following text -file. Copy it out of your browser and save it as jayne.txt:
+file. Copy it out of your browser and save it as jayne.txt:To: George Shmidlap From: Rita Marlowe @@ -828,7 +834,7 @@ mailing list.@@ -839,7 +845,7 @@ built-in decompression as it can be painfully slow for large archives. [1] We recommend -downloading boost_1_44_0.7z and using 7-Zip to decompress +downloading boost_1_44_0.7z and using 7-Zip to decompress it. We no longer recommend .zip files for Boost because they are twice as large as the equivalent .7z files. We don't recommend using Windows' built-in decompression as it can be painfully slow for large archives. @@ -856,21 +862,21 @@ used in the examples. [2] If you used the installer from Boost Consulting and deselected “Source and Documentation” (it's -selected by default), you won't see the libs/ subdirectory. +selected by default), you won't see the libs/ subdirectory. That won't affect your ability to use precompiled binaries, but you won't be able to rebuild libraries from scratch.
- [4] In this example, the caret character ^ is a +
[4] In this example, the caret character ^ is a way of continuing the command on multiple lines, and must be the final character used on the line to be continued (i.e. do not follow it with spaces). The command prompt responds with -More? to prompt for more input. Feel free to omit the +More? to prompt for more input. Feel free to omit the carets and subsequent newlines; we used them so the example would fit on a page of reasonable width.
The command prompt treats each bit of whitespace in the command -as an argument separator. That means quotation marks (") +as an argument separator. That means quotation marks (") are required to keep text together whenever a single command-line argument contains spaces, as in
--build-dir="C:\Documents_and_Settings\dave\build-boost"-Also, for example, you can't add spaces around the = sign as in
+Also, for example, you can't add spaces around the = sign as in
--build-dir_=_"C:\Documents and Settings\dave\build-boost"@@ -905,7 +911,7 @@ same name.@@ -933,6 +939,8 @@ recommend it. + + [7] These libraries were compiled without optimization or inlining, with full debug symbols enabled, and without -NDEBUG #defined. Although it's true that sometimes +NDEBUG #defined. Although it's true that sometimes these choices don't affect binary compatibility with other compiled code, you can't count on that with Boost libraries.