finding libraries for programs with doing clean builds

[Matt Rogers]

On Fri, Jan 06, 2006 at 12:00:11PM -0200, Thiago Macieira wrote:
> Matt Rogers wrote:
> >I've tried to think of a good solution for this for the last couple of
> > days and I haven't come up with much of anything. Does anybody else
> > have some ideas on how to solve this? Obviously setting LD_LIBRARY_PATH
> > before running scons works, but there will be a lot of directories that
> > will need to be added once we get around to doing things like compiling
> > docs, etc. and I'm wondering if we can do something better.
> 
> The only solution is to duplicate what libtool does, which is to determine 
> how to run a program linked against uninstalled libraries.
> 
> Options are:
> 1) setting the proper environment variable when possible 
> (DYLIB_LIBRARY_PATH, LD_LIBRARY_PATH, etc.)
> 

I'm setting LD_LIBRARY_PATH manually at the moment, which works. If we
wanted to do it this way, I think it'd be best to see if there's a way
to automate the process of setting LD_LIBRARY_PATH.

> 2) relinking the program if no other suitable method is found
> 
> Note that a standard Linux uses option #2, because LD_LIBRARY_PATH won't 
> work on a standard KDE installation that used --rpath.
> 

but when does it relink it? at install time?

> Also note that the fact that we run program we've just built makes it 
> impossible to do a KDE cross-compilation. The clean solution for this 
> would be to split all programs we need for building KDE from the KDE 
> build itself.
> 

And I might get killed for saying this, but what about just continuing
to use libtool as part of the build process? Surely we could hack
something into bksys to do this.

--
Matt