Re: [Boost-build] problem with installing

Subject: Re: [Boost-build] problem with installing
From: Shridhar Daithankar (ghodechhap_at_[hidden])
Date: 2010-05-29 01:56:50

On Friday 28 May 2010 09:32:45 Shridhar Daithankar wrote:
> Hello,
> 
> I have a multi-module project with each module defining its own install and
> the jamroot ties them together with an alias, as follows
> 
> alias install : /cms/utils//install /cms/db//install /cms/core//install
> /cms/h2//install /cms/player//install ;
> 
> I am getting the attached error when I run
> $ bjam -n --prefix=/home/shridhar/ install
> 
> Previously when I encountered this problem I removed a module from top
> level definition to fix it and I accepted it as a workaround. This time
> also, removing player module from top level fixes the problem.
> 
> I want to fix this and not work around. Any help?

replying to self here, 

I tried to perform install on one of the module player and here is what I 
got(actual actions omitted for simplicity)

----------------------------
$ bjam -n --prefix=/home/shridhar /cms/player//install
...patience...
...patience...
...found 4560 targets...
...updating 5 targets...
gcc.link.dll /home/shridhar/lib/libcmsutils.so
gcc.link.dll /home/shridhar/lib/libcmsdb.so
gcc.link.dll /home/shridhar/lib/libcmscore.so
common.copy /home/shridhar/lib/libcmsplayer.so

...updated 5 targets...
----------------------------

I do not understand why 3 libraries are relinked during installation. 
Relinking a binary is understandable but why libraries?

Since multiple modules are doing link on same library during installation and 
there is a copy too, the original error of duplicate target name is reported.

Here is definition of libcmsutils.so

-----------------
lib dl ;
lib ssl ;
lib cmsutils : filebuffer.cpp library.cpp executor.cpp
        dl ssl
        /boost//filesystem/<variant>release
        : <include>include ;

import package ;
package.install install : : : cmsutils ;
explicit install ;
-----------------

No dependent objects or libraries were updated between build and install. So 
why a relink on that library is triggered during installation?

-- 
Regards 
 Shridhar