Re: [Boost-users] Re: python library issue migrating from boost_1_30_2 to boost_1_31_0

From: Marco Donizelli (maleko_at_[hidden])
Date: 2004-03-08 07:07:48

Rene Rivera wrote:

>
> That depends on which previous version of libboost_python.so you want 
> to be compatible with. Previously two versions still got built, both 
> named the same, but in different directories. So which one are you 
> referring to? The single threaded, or multi-threaded? 

Dear Rene, thanks a lot for your answer. When I built the Python
library within Boost version 1.30.02, the result of the build is:

 > cd ./bin-stage ; ls -l ; cd -
total 28992
-rw-r--r--    1 maleko   compneur   432470 Mar  8 11:09 libboost_python.a
-rw-r--r--    1 maleko   compneur 12962852 Mar  8 11:08 
libboost_python_debug.a
-rwxr-xr-x    1 maleko   compneur  7877213 Mar  8 11:05 
libboost_python_debug.so
-rwxr-xr-x    1 maleko   compneur  7877213 Mar  8 11:05 
libboost_python_debug.so.1.30.2
-rwxr-xr-x    1 maleko   compneur   241652 Mar  8 11:06 libboost_python.so
-rwxr-xr-x    1 maleko   compneur   241652 Mar  8 11:06 
libboost_python.so.1.30.2

 > cd 
./bin/libboost_python.so/gcc/debug/runtime-link-dynamic/shared-linkable-true/ 
; ls -l *so*; cd -
lrwxrwxrwx    1 maleko   compneur       31 Mar  8 11:05 
libboost_python_debug.so -> libboost_python_debug.so.1.30.2
-rwxr-xr-x    1 maleko   compneur  7877213 Mar  8 11:05 
libboost_python_debug.so.1.30.2
lrwxrwxrwx    1 maleko   compneur       25 Mar  8 11:10 
libboost_python.so -> libboost_python.so.1.30.2
-rwxr-xr-x    1 maleko   compneur  7877213 Mar  8 11:10 
libboost_python.so.1.30.2

 > cd 
./bin/libboost_python.so/gcc/release/runtime-link-dynamic/shared-linkable-true/ 
; ls -l *so* ; cd -
lrwxrwxrwx    1 maleko   compneur       25 Mar  8 11:06 
libboost_python.so -> libboost_python.so.1.30.2
-rwxr-xr-x    1 maleko   compneur   241652 Mar  8 11:06 
libboost_python.so.1.30.2

so, i got basicly two libraries, the debug one and the release one, but 
I do not notice anything about
multithreading. again, am I on the wrong track due to a build & 
installation mistake?

> And by the way just having the name match does not give you backward 
> compatibility. The really important aspect is binary compatibility. 
> For that you need to rebuild your modules+applications, as Boost/C++ 
> doesn't really have a concept of binary backward compatibility. 

thanks for the advice.
marco