Question on installed libraries and dependent programs

Hi

I'm not sure if this is the expected behaviour but should a
program that's 
dependent on an installed library relink when the installed
library has been 
updated.

To explain I modified "example/libraries"

./Jamroot
---------
use-project /library-example/foo : util/foo ;

build-project app ;

lib instbar : : <name>bar <search>install ;


util/foo/Jamfile
----------------
project 
    : usage-requirements <include>include ;

lib bar : bar.cpp ;

install install : bar : <location>../../install ;


app/Jamfile
-----------
exe app : app.cpp ..//instbar :
<include>../util/foo/include ;

I then build (separately) util/foo and app. 
I return to util/foo and rebuild the library ( bjam clean;
bjam ).
I then return to app and type bjam but app does not relink.
Should it ?


Thanks
Hassan





_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Hassan Mehmet wrote:

> Hi
> 
> I'm not sure if this is the expected behaviour but
should a program that's
> dependent on an installed library relink when the
installed library has
> been updated.
> 
> To explain I modified "example/libraries"
> 
> ./Jamroot
> ---------
> use-project /library-example/foo : util/foo ;
> 
> build-project app ;
> 
> lib instbar : : <name>bar <search>install
;
> 
> 
> util/foo/Jamfile
> ----------------
> project
>     : usage-requirements <include>include ;
> 
> lib bar : bar.cpp ;
> 
> install install : bar : <location>../../install
;
> 
> 
> app/Jamfile
> -----------
> exe app : app.cpp ..//instbar :
<include>../util/foo/include ;

'instbar' here refers to:

        lib instbar : : <name>bar
<search>install ;

which definition say 'ask the linker to search for library
bar
in directory install'. However, Boost.Build has no idea how
the linker actually does it -- the linker can find this
library
in some "standard" directory, for example.
Therefore, it's not
possible to establish dependency on instbar.

Referring to 'util/foo//install' should work better.

- Volodya



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus <ghost <at> cs.msu.su> writes:

>  
> Referring to 'util/foo//install' should work better.
> 

Thanks Voldoya

That also solved another problem we had with the
"error: No best alternative" 
issue 


We no longer have to rename installed debug libraries to
xxx_d.a because we 
can get the library directly from it's install target
instead of using 
<search>.


Cheers
Hassan



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build