Use the latest version of this Getting Started guide
The Boost website version of this Getting Started guide may have updated information, such as the location of additional installers diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html index ace95d9ef6..f988c983cd 100644 --- a/more/getting_started/unix-variants.html +++ b/more/getting_started/unix-variants.html @@ -3,7 +3,7 @@
- +Other Packages
RedHat, Debian, and other distribution packagers supply Boost library packages, however you may need to adapt these @@ -94,7 +94,7 @@ from + `` `` libs/ ............Tests, .cpps, docs, etc., by library index.html ........Library documentation starts here algorithm/ @@ -141,7 +141,7 @@ sometimes referred to as $BOOST_ROOT in docume 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 @@ -154,7 +154,7 @@ Boost #include directives will look like:
#include "boost/whatever.hpp"depending on your preference regarding the use of angle bracket -includes.
+includes. `` ``Don't be distracted by the doc/ subdirectory; it only contains a subset of the Boost documentation. Start with @@ -169,7 +169,7 @@ contains a subset of the Boost documentation. Start with
The first thing many people want to know is, “how do I build Boost?” The good news is that often, there's nothing to build.
-Nothing to Build?
Most Boost libraries are header-only: they consist entirely of header files containing templates and inline functions, and @@ -192,7 +192,6 @@ treatment when linking.
before building and installing it)First, find the toolset corresponding to your compiler in the following table (an up-to-date list is always available in the Boost.Build documentation).
-Note
If you previously chose a toolset for the purposes of building b2, you should assume it won't work and instead @@ -407,7 +406,7 @@ the Apache standard library in C++03 mode use
If you have multiple versions of a particular compiler installed, you can append the version number to the toolset name, preceded by a hyphen, e.g. intel-9.0 or -borland-5.4.3.
+borland-5.4.3. `` ``Change your current directory to the Boost root directory and invoke b2 as follows:
-b2 --build-dir=build-directory toolset=toolset-name stage +b2 --build-dir=build-directory toolset=toolset-name `` `` stage
For a complete description of these and other invocation options, please see the Boost.Build documentation.
@@ -439,7 +438,7 @@ $ b2 --build-dir=/tmp/build-boost toolset=gcc library binaries in the stage/lib/ subdirectory of the Boost tree. To use a different directory pass the --stagedir=directory option to b2. -Note
b2 is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.
@@ -457,7 +456,7 @@ be interested in:Note
Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure @@ -787,7 +786,7 @@ mailing list.
Onward
Good luck, and have fun!
diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html index 99efee9628..01f31b5c97 100644 --- a/more/getting_started/windows.html +++ b/more/getting_started/windows.html @@ -3,7 +3,7 @@ - +Boost Getting Started on Windows @@ -14,7 +14,7 @@ -+A note to Cygwin and MinGW users
If you plan to use your tools from the Windows command prompt, you're in the right place. If you plan to build from the Cygwin @@ -154,7 +154,7 @@ contains a subset of the Boost documentation. Start with
3 Header-Only Libraries
The first thing many people want to know is, “how do I build Boost?” The good news is that often, there's nothing to build.
-+Nothing to Build?
Most Boost libraries are header-only: they consist entirely of header files containing templates and inline functions, and @@ -177,7 +177,6 @@ treatment when linking.
before building and installing it)Boost.Regex Boost.Serialization -Boost.Signals Boost.Thread Boost.Timer Boost.Wave @@ -230,7 +229,7 @@ int main() }Copy the text of this program into a file called example.cpp.
-+Note
To build the examples in this guide, you can use an Integrated Development Environment (IDE) like Visual Studio, or @@ -389,7 +388,7 @@ the directory where you want Boost.Build to be installed
First, find the toolset corresponding to your compiler in the following table (an up-to-date list is always available in the Boost.Build documentation).
-+Note
If you previously chose a toolset for the purposes of building b2, you should assume it won't work and instead @@ -508,7 +507,7 @@ list.
library binaries in the stage\lib\ subdirectory of the Boost tree. To use a different directory pass the --stagedir=directory option to b2. -+Note
b2 is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.
@@ -526,7 +525,7 @@ be interested in: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 @@ -609,7 +608,7 @@ build settings. whose compile configuration is compatible with the rest of your project. -
+Auto-Linking
Most Windows compilers and linkers have so-called “auto-linking support,” which eliminates the second challenge. Special code in @@ -648,7 +647,7 @@ cl /EHsc /I path\to\boost_1_71_0 exam
6.3 Library Naming
-+Note
If, like Visual C++, your compiler supports auto-linking, you can probably skip to the next step.
@@ -857,7 +856,7 @@ mailing list.Boost.Build mailing list Index of all Boost library documentation -+Onward
Good luck, and have fun!