Update of /cvsroot/boost/boost/more/getting_started/detail
In directory
sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv23652/more/getting_started/detail
Modified Files:
library-naming.rst header-only.rst build-from-source-head.rst
Log Message:
Some progress on Python build guide. Minor fixes to getting started guide.
Index: library-naming.rst
===================================================================
RCS file: /cvsroot/boost/boost/more/getting_started/detail/library-naming.rst,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- library-naming.rst 22 Dec 2006 16:26:47 -0000 1.2
+++ library-naming.rst 11 Apr 2007 23:35:08 -0000 1.3
@@ -19,7 +19,7 @@
*Library name*: all boost library filenames begin with ``boost_``.
``-vc71``
- *Toolset tag*: identifies the toolset and version used to build
+ *Toolset tag*: identifies the toolset_ and version used to build
the binary.
``-mt``
@@ -68,13 +68,13 @@
``.a`` and ``.so`` for static libraries (archives) and shared
libraries, respectively. On Windows, ``.dll`` indicates a shared
library and (except for static libraries built by the ``gcc``
- toolset, whose names always end in ``.a``) ``.lib`` indicates a
+ toolset_, whose names always end in ``.a``) ``.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
version number, will also be created.
-.. _Boost.Build toolset names: toolset-name_
+.. .. _Boost.Build toolset names: toolset-name_
__ ../../libs/python/doc/building.html#variants
Index: header-only.rst
===================================================================
RCS file: /cvsroot/boost/boost/more/getting_started/detail/header-only.rst,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- header-only.rst 22 Dec 2006 14:52:22 -0000 1.1
+++ header-only.rst 11 Apr 2007 23:35:08 -0000 1.2
@@ -15,20 +15,23 @@
require no separately-compiled library binaries or special
treatment when linking.
-.. _separate:
+.. .. _separate:
The only Boost libraries that *must* be built separately are:
* Boost.Filesystem_
* Boost.IOStreams_
* Boost.ProgramOptions_
-* Boost.Python_
+* Boost.Python_ (see the `Boost.Python build documentation`__
+ before building and installing it)
* Boost.Regex_
* Boost.Serialization_
* Boost.Signals_
* Boost.Thread_
* Boost.Wave_
+__ ../../libs/python/doc/building.html
+
A few libraries have optional separately-compiled binaries:
* Boost.DateTime_ has a binary component that is only needed if
Index: build-from-source-head.rst
===================================================================
RCS file:
/cvsroot/boost/boost/more/getting_started/detail/build-from-source-head.rst,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- build-from-source-head.rst 22 Dec 2006 14:52:22 -0000 1.1
+++ build-from-source-head.rst 11 Apr 2007 23:35:08 -0000 1.2
@@ -10,7 +10,7 @@
.. _precompiled-bjam:
http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941
-.. _Boost.Jam documentation: Boost.Jam_
+.. .. _Boost.Jam documentation: Boost.Jam_
.. _Boost.Build: ../../tools/build/index.html
.. _Boost.Jam: ../../tools/jam/index.html
.. _Boost.Build documentation: Boost.Build_
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Boost-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/boost-cvs
