Re: [Boost-build] hardcode-dll-paths in shared lib

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-12-28 05:34:45

On Thursday 28 December 2006 11:49, Jorge Suit Perez Ronda wrote:
> On Thu, 2006-12-28 at 11:22 +0300, Vladimir Prus wrote:
> > On Thursday 28 December 2006 05:18, Jorge Suit Perez Ronda wrote:
> > > Hello, I build a shared lib A which use a prebuilt shared lib B. The lib
> > > is installed in a non-standard place /usr/local/B/lib
> > > 
> > > lib B : : <search>/usr/local/B/lib ;
> > > lib A : sources_of_A B ;
> > > exe C : sources_of_C A ;
> > > 
> > > when the project is built C "know" where B is, but A does not "know"
> > > where B is. Is there a way that B location be "hardcoded" into A in the
> > > same way as it is in C?
> > 
> > In theory, 'C' should have paths both to A and B, and so all libraries
> > should be found. 
> > 
> > Is this not happening?
> 
> yes it is

Oh, good. At least it's not a bug then.

> 
> >  Or you want 'A' to hardcode path to 'B' so that
> > it can be used outside 'C'?
> 
> yes also, I want to use A outside C. Any way to hardcode B into A?

Not now. I did not want to hardcode paths into libs, since otherwise
you have to relink the libraries when installing, to remove hardcoding.
Now, we also relink libraries.

Do you think we should just hardcode into both exe and lib and relink both,
or have some special syntax to indicate that the library should be usable
on its own?

- Volodya

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