[pkg-boost-commits] r14368 - boost/trunk/debian
smr at alioth.debian.org
smr at alioth.debian.org
Mon Feb 16 22:05:43 UTC 2009
Author: smr
Date: 2009-02-16 22:05:43 +0000 (Mon, 16 Feb 2009)
New Revision: 14368
Modified:
boost/trunk/debian/README.Debian
boost/trunk/debian/changelog
boost/trunk/debian/libboost-python-dev.README.Debian
Log:
Update READMEs, removing verbiage about decorated/simplified link names.
Modified: boost/trunk/debian/README.Debian
===================================================================
--- boost/trunk/debian/README.Debian 2009-01-11 07:39:13 UTC (rev 14367)
+++ boost/trunk/debian/README.Debian 2009-02-16 22:05:43 UTC (rev 14368)
@@ -10,82 +10,55 @@
Getting Started
---------------
-One of the main goals of Boost is source portability across operating
-systems and compilers. Nothing is instead guaranted about binary
-compatibility, which in C++ is much more difficult topic than in C.
-
-To protect users from harming themselves, Boost developers encode as
-much information as possible in the library names. So Boost libraries
-get scary names like libboost_wserialization-gcc42-mt-d-1_34_1.so.1.34.1.
-
-Please refer to the Boost documentation in order to understand how to
-build the library name you are looking for:
-
- http://www.boost.org/more/getting_started/unix-variants.html#library-naming
-
-Currently does not exist a portable and automatic way to build these
-names. You may guess pkg-config may be of help here but work is still
-in progress.
-
-
-Unportable Debian-specific way to solve the above problem
----------------------------------------------------------
-
The following table shows which components use a library (shared or
-static) and the corresponding "-l" flag.
+static) and the corresponding "-l" flag. Note that only the
+multithreaded version of the libraries is shipped.
-Beware that every library comes in two flavors, one for single-thread
-and one for multi-thread uses (except Boost.Thread, which is only
-multi-thread). To the following "-l" flags you need to append -mt in
-case the multi-thread flavour is wanted (e.g. -lboost_date_time for
-single-thread, -lboost_date_time-mt for multi-thread).
-
Component Link Flag Library Type
--------- --------- ------------
- Boost.Date_time -lboost_date_time static shared
- Boost.Filesystem -lboost_filesystem static shared
- Boost.Graph -lboost_graph static shared
- Boost.IOStreams -lboost_iostreams static shared
- Boost.Program_options -lboost_program_options static shared
- Boost.Python -lboost_python static shared
- Boost.Regex -lboost_regex static shared
- Boost.Serialization -lboost_serialization static shared
- -lboost_wserialization static shared
- Boost.Signals -lboost_signals static shared
- Boost.Test -lboost_prg_exec_monitor static shared
- -lboost_unit_test_framework static shared
- Boost.Thread -lboost_thread static shared
- Boost.Wave -lboost_wave static shared
+ Boost.Date_Time -lboost_date_time-mt static shared
+ Boost.Filesystem -lboost_filesystem-mt static shared
+ Boost.Graph -lboost_graph-mt static shared
+ Boost.IOStreams -lboost_iostreams-mt static shared
+ Boost.Math -lboost_math_c99-mt static shared
+ -lboost_math_c99f-mt static shared
+ -lboost_math_c99l-mt static shared
+ Boost.MPI -lboost_mpi-mt static shared
+ Boost.Program_options -lboost_program_options-mt static shared
+ Boost.Python -lboost_python-mt-py24 static shared
+ -lboost_python-mt-py25 static shared
+ Boost.Regex -lboost_regex-mt static shared
+ Boost.Serialization -lboost_serialization-mt static shared
+ -lboost_wserialization-mt static shared
+ Boost.Signals -lboost_signals-mt static shared
+ Boost.System -lboost_system-mt static shared
+ Boost.Test -lboost_prg_exec_monitor-mt static shared
+ -lboost_unit_test_framework-mt static shared
+ Boost.Thread -lboost_thread-mt static shared
+ Boost.Wave -lboost_wave-mt static shared
-Most of Boost is installed using the package libboost-dev.
+Most of Boost is installed using the package libboostX.Y-dev.
The components with a shared library have separate -dev packages.
-There is extensive documentation available in the libboost-doc
+There is extensive documentation available in the libboostX.Y-doc
package and at www.boost.org.
-Threaded Applications
----------------------
-
-You need to specify -pthread switch on the gcc command line to build
-multi-thread applications. Remember to use the -mt library flavour.
-
-
Example Code
------------
-All example code is shipped in libboost-doc package.
+All example code is shipped in libboostX.Y-doc package.
Some of the example code is linked to by the documentation, and thus
appears in a directory named
- /usr/share/doc/libboost-doc/HTML/libs/*/example
+ /usr/share/doc/libboostX.Y-doc/HTML/libs/*/example
Example code that is not linked from the documentation appears in a
directory under
- /usr/share/doc/libboost-doc/examples/libs/
+ /usr/share/doc/libboostX.Y-doc/examples/libs/
Use of boost/nondet_random.hpp
@@ -95,10 +68,10 @@
boost::random_device::impl. Boost libraries provide only an example
implementation which the user may use to fit her needs.
-Such implementation is distributed by libboost-dev Debian package in
-file /usr/share/doc/libboost-dev/examples/random_device.cpp. This file is
-generally good enough for most linux users. Please add it to your build
-process before filing another bug report against Boost Debian packages.
+Such implementation is distributed by libboostX.Y-dev Debian package
+in file /usr/share/doc/libboostX.Y-dev/examples/random_device.cpp.
+This file is generally good enough for most linux users. Simply
+copy and modify to suit your needs.
- -- Steve M. Robbins <smr at debian.org>, Fri, 21 Mar 2008 11:18:32 z
+ -- Steve M. Robbins <smr at debian.org>, Mon, 16 Feb 2009 15:53:46 z
Modified: boost/trunk/debian/changelog
===================================================================
--- boost/trunk/debian/changelog 2009-01-11 07:39:13 UTC (rev 14367)
+++ boost/trunk/debian/changelog 2009-02-16 22:05:43 UTC (rev 14368)
@@ -1,3 +1,12 @@
+boost1.37 (1.37.0-5) unstable; urgency=low
+
+ * README.Debian:
+ * libboost-python-dev.README.Debian: Revise, removing all the verbiage
+ about single-threaded versions and decorated library names which was
+ not relevant as of 1.37.0-1.
+
+ -- Steve M. Robbins <smr at debian.org> Mon, 16 Feb 2009 15:55:23 -0600
+
boost1.37 (1.37.0-4) unstable; urgency=low
* patches/function-template.patch: New. Fix misplaced #ifdef (thanks to
Modified: boost/trunk/debian/libboost-python-dev.README.Debian
===================================================================
--- boost/trunk/debian/libboost-python-dev.README.Debian 2009-01-11 07:39:13 UTC (rev 14367)
+++ boost/trunk/debian/libboost-python-dev.README.Debian 2009-02-16 22:05:43 UTC (rev 14368)
@@ -3,22 +3,17 @@
The Debian Boost.Python packages support python versions: 2.4, 2.5.
-As is typical of Boost (see /usr/share/doc/libboost-dev/README.Debian)
-the library names encode the boost version, gcc version, thread
-support, and the like. The upstream names do NOT encode the python
-version. However, for Debian to support multiple Python runtimes, we
-do need to encode the python version.
+This is achieved by decorating the library names with the python
+version. You can choose either to use Boost.Python with a specific
+Python version, or use the default Python version.
+
Choosing the default Python
---------------------------
-To keep backwards compatibility, the standard upstream link library
-names are generated as symlinks to the default python version.
+You may simply link with -lboost_python. This will always be the
+default python version.
-If you want to use the non-standard Debian-specific simplified
-library names, you may simply link with -lboost_python. This
-will always be the default python version.
-
These default symlinks are automatically updated when the Python
runtime version changes.
@@ -30,8 +25,7 @@
select the specific Python version desired. This holds true
for both the upstream names and the simplified Debian names.
-So if you want to use the simplified names, link against
--lboost_python-py24 for Python 2.4.
+So link against -lboost_python-py24 for Python 2.4.
- -- Steve M. Robbins <smr at debian.org>, Fri, 21 Mar 2008 13:33:53 z
+ -- Steve M. Robbins <smr at debian.org>, Mon, 16 Feb 2009 16:04:22 z
More information about the pkg-boost-commits
mailing list