[ Please Cc me on replies, I'm not subbed up to list. ]
Hi libtool team,
Windows DLLs, unlike Linux DSOs, have to live in the bin directory (or
elsewhere on $PATH), not the lib dir. Libtool handles this at --link time by
setting the dlname in the generated .la file to a relative path
Dave Korn wrote:
[ Please Cc me on replies, I'm not subbed up to list. ]
Windows DLLs, unlike Linux DSOs, have to live in the bin directory (or
elsewhere on $PATH), not the lib dir. Libtool handles this at --link time by
setting the dlname in the generated .la file to a relative path
Charles Wilson wrote:
[ snip ]
Thanks for all the shell portability advice, it's pretty specialised stuff
that I don't know all about; I'll incorporate your changes into the respin when
I add the docs.
I'm not sure -rpath is the right way to test, here. I know you're
trying to avoid doing
Dave Korn wrote:
Well, I did really want to make it a test of nothing other than the -bindir
functionality, in fact it's more or less just a test of the corner cases for
func_relative_path! Using -rpath seems to work as far as supplying an input
value for $install_libdir and that's all I