Update version info in the getting started guide.

[SVN r47870]
This commit is contained in:
Daniel James 2008-07-29 20:37:22 +00:00
parent a5784f18c1
commit f6a7f522ad
2 changed files with 5 additions and 5 deletions

View File

@ -5,8 +5,8 @@
.. This file contains all the definitions that need to be updated
.. for each new release of Boost.
.. |boost-version-number| replace:: 1.35.0
.. |boost_ver| replace:: ``boost_1_35_0``
.. |boost_ver-bold| replace:: **boost_1_35_0**
.. |boost-version-number| replace:: 1.36.0
.. |boost_ver| replace:: ``boost_1_36_0``
.. |boost_ver-bold| replace:: **boost_1_36_0**
.. _sf-download: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041

View File

@ -153,7 +153,7 @@ A. You can specify the full path to each library:
.. parsed-literal::
$ c++ -I |root| example.cpp -o example **\\**
**~/boost/lib/libboost_regex-gcc34-mt-d-1_35.a**
**~/boost/lib/libboost_regex-gcc34-mt-d-1_36.a**
B. You can separately specify a directory to search (with ``-L``\
*directory*) and a library name to search for (with ``-l``\
@ -163,7 +163,7 @@ B. You can separately specify a directory to search (with ``-L``\
.. parsed-literal::
$ c++ -I |root| example.cpp -o example **\\**
**-L~/boost/lib/ -lboost_regex-gcc34-mt-d-1_35**
**-L~/boost/lib/ -lboost_regex-gcc34-mt-d-1_36**
As you can see, this method is just as terse as method A for one
library; it *really* pays off when you're using multiple