This release includes 1 new library - (VMD), +
The release includes 4 new libraries + (Compute, + DLL, + Hana, + Metaparse), as well as updates to many existing libraries. See Release History for more information.
diff --git a/libs/libraries.htm b/libs/libraries.htm index 0cefcb37dc..322a58e1dd 100644 --- a/libs/libraries.htm +++ b/libs/libraries.htm @@ -127,7 +127,7 @@ how to download, build, and install the libraries.The most reliable way to get a copy of Boost is to download a -distribution from SourceForge:
+distribution from SourceForge:Download boost_1_60_0.tar.bz2.
+Download boost_1_61_0.tar.bz2.
In the directory where you want to put the Boost installation, execute
-tar --bzip2 -xf /path/to/boost_1_60_0.tar.bz2 +tar --bzip2 -xf /path/to/boost_1_61_0.tar.bz2
This is a sketch of the resulting directory structure:
-boost_1_60_0/ .................The “boost root directory”
+boost_1_61_0/ .................The “boost root directory”
index.htm .........A copy of www.boost.org starts here
boost/ .........................All Boost Header files
@@ -136,7 +136,7 @@ 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_60_0) is
+
The path to the boost root directory (often /usr/local/boost_1_61_0) is
sometimes referred to as $BOOST_ROOT in documentation and
mailing lists .
Now, in the directory where you saved example.cpp, issue the
following command:
-c++ -I path/to/boost_1_60_0 example.cpp -o example
+c++ -I path/to/boost_1_61_0 example.cpp -o example
To test the result, type:
@@ -276,7 +276,7 @@ you'll need to acquire library binaries.
Issue the following commands in the shell (don't type $; that
represents the shell's prompt):
-$ cd path/to/boost_1_60_0
+$ cd path/to/boost_1_61_0
$ ./bootstrap.sh --help
Select your configuration options and invoke ./bootstrap.sh again
@@ -306,11 +306,6 @@ need to use Bo
You'll also
use this method if you need a nonstandard build variant (see the
Boost.Build documentation for more details).
-
-Boost.CMake
-There is also an experimental CMake build for boost, supported and distributed
-separately. See the Boost.CMake wiki page for more information.
-
@@ -430,7 +425,7 @@ b2 --build-dir=b
please see the Boost.Build documentation.
For example, your session might look like this:
-$ cd ~/boost_1_60_0
+$ cd ~/boost_1_61_0
$ b2 --build-dir=/tmp/build-boost toolset=gcc stage
That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “--build-type=complete”.
@@ -546,14 +541,14 @@ project.
You can specify the full path to each library:
-$ c++ -I path/to/boost_1_60_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_61_0 example.cpp -o example \
~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.a
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_60_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_61_0 example.cpp -o example \
-L~/boost/stage/lib/ -lboost_regex-gcc34-mt-d-1_36
As you can see, this method is just as terse as method A for one
diff --git a/more/getting_started/unix-variants.rst b/more/getting_started/unix-variants.rst
index 40f6f228d4..6cc7bc9735 100644
--- a/more/getting_started/unix-variants.rst
+++ b/more/getting_started/unix-variants.rst
@@ -135,14 +135,6 @@ You'll also
use this method if you need a nonstandard build variant (see the
`Boost.Build documentation`_ for more details).
-.. Admonition:: Boost.CMake
-
- There is also an experimental CMake build for boost, supported and distributed
- separately. See the `Boost.CMake`_ wiki page for more information.
-
- .. _`Boost.CMake`:
- https://svn.boost.org/trac/boost/wiki/CMake
-
.. include:: detail/build-from-source-head.rst
For example, your session might look like this:
diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html
index 1c2a495f28..f110e85c74 100644
--- a/more/getting_started/windows.html
+++ b/more/getting_started/windows.html
@@ -61,7 +61,7 @@ not supported—they may or may not work.
1 Get Boost
The most reliable way to get a copy of Boost is to
-download boost_1_60_0.7z or boost_1_60_0.zip and unpack it to install a complete Boost
+download boost_1_61_0.7z or boost_1_61_0.zip and unpack it to install a complete Boost
distribution.1
@@ -71,7 +71,7 @@ distribution.1
2 The Boost Distribution
This is a sketch of the resulting directory structure:
-boost_1_60_0\ .................The “boost root directory”
+boost_1_61_0\ .................The “boost root directory”
index.htm .........A copy of www.boost.org starts here
boost\ .........................All Boost Header files
lib\ .....................precompiled library binaries
@@ -116,7 +116,7 @@ anything you can use in these directories.
It's important to note the following:
-The path to the boost root directory (often C:\Program Files\boost\boost_1_60_0) is
+
The path to the boost root directory (often C:\Program Files\boost\boost_1_61_0) is
sometimes referred to as $BOOST_ROOT in documentation and
mailing lists .
followed by Return. For example,
-cd C:\Program Files\boost\boost_1_60_0
+cd C:\Program Files\boost\boost_1_61_0
Long commands can be continued across several lines by typing a
caret (^) at the end of all but the last line. Some examples
@@ -280,7 +280,7 @@ select Properties from the resulting pop-up menu
In Configuration Properties > C/C++ > General > Additional Include
Directories, enter the path to the Boost root directory, for example
-C:\Program Files\boost\boost_1_60_0
+C:\Program Files\boost\boost_1_61_0
In Configuration Properties > C/C++ > Precompiled Headers, change
@@ -318,7 +318,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_60_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_61_0 path\to\example.cpp
To test the result, type:
@@ -365,11 +365,6 @@ of allowed options.
If you're using an earlier version of Visual C++, or a compiler
from another vendor, you'll need to use Boost.Build to create your
own binaries.
-
-Boost.CMake
-There is also an experimental CMake build for boost, supported and distributed
-separately. See the Boost.CMake wiki page for more information.
-
@@ -492,8 +487,8 @@ b2 --build-dir=b
please see the Boost.Build documentation.
For example, your session might look like this:3
-C:\WINDOWS> cd C:\Program Files\boost\boost_1_60_0
-C:\Program Files\boost\boost_1_60_0> b2 ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_61_0
+C:\Program Files\boost\boost_1_61_0> b2 ^
More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
More? --build-type=complete msvc stage
@@ -632,7 +627,7 @@ earlier:
select Properties from the resulting pop-up menu
- In Configuration Properties > Linker > Additional Library
Directories, enter the path to the Boost binaries,
-e.g. C:\Program Files\boost\boost_1_60_0\lib\.
+e.g. C:\Program Files\boost\boost_1_61_0\lib\.
- From the Build menu, select Build Solution.
@@ -642,10 +637,10 @@ e.g. C:\Program Files\boos
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_60_0\lib:
+in C:\Program Files\boost\boost_1_61_0\lib:
-cl /EHsc /I path\to\boost_1_60_0 example.cpp ^
- /link /LIBPATH:C:\Program Files\boost\boost_1_60_0\lib
+cl /EHsc /I path\to\boost_1_61_0 example.cpp ^
+ /link /LIBPATH:C:\Program Files\boost\boost_1_61_0\lib
@@ -801,7 +796,7 @@ mailing list.
[1] We recommend
-downloading boost_1_60_0.7z and using 7-Zip to decompress
+downloading boost_1_61_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.