Re: Setting environment variable in libtool wrapper?

[Geoffrey Hutchison]

Hi Ralf,

> Would it also load modules without specifying a directory?  IOW: would
> adjusting the uninstalled program's DT_RPATH (or equivalent) or
> LD_LIBRARY_PATH (or equivalent) be sufficient, too?

Currently, no. But that's an easy change.

> With those two new flags, it would be possible to seamlessly support
> mixing of libtool libraries and non-libtool libraries in one build, as
> well as libltdl modules and non-libltdl modules.  I think.  GCC needs
> the former, for example.

Yes, this would be good.

In the meantime, can you think of any way to handle a workaround?  
Maybe something like install-hook in Automake that would allow me to  
add an "export ${VAR}" after "make" is run? If I hack ltmain.sh, will  
autoconf variables be substituted (i.e., hand-editing the binary  
libtool wrapper in ltmain.sh)?

One possibility that occurred to me was to kludge BUILT_SOURCES to  
create a dummy header and export the environment variable there. But  
it might cover 80% of users/developers who just run "make all".

Thanks,
-Geoff