Re: Re: hardcode_libdir, rpath and DLLs

2006-04-28 Thread Robert Szeleney
Hi! Ok, because of the various problems using PE/DLL executable format with *nix software I just decided to completely drop PE support and replace it with ELF. (Except for a tiny .PE loader for Mono assemblies). http://www.skyos.org/?q=node/519 Once done, I will try porting libtool again and le

Re: Re: hardcode_libdir, rpath and DLLs

2006-04-27 Thread Ralf Wildenhues
Hi Robert, * Robert Szeleney wrote on Thu, Apr 27, 2006 at 12:11:45PM CEST: > > >>> Unfortunately, PE DLLs don't support this --rpath option. Is there any > >>> way to tell libtool to use something different for this? > >> I suspect the right way to handle this would be to use "libtool > >> --mo

Re: Re: hardcode_libdir, rpath and DLLs

2006-04-27 Thread Robert Szeleney
Hi Brian! >>> Unfortunately, PE DLLs don't support this --rpath option. Is there any >>> way to tell libtool to use something different for this? >>> >>> Probably using LD_LIBRARY_PATH. Though I think that this will not >>> really work, because whenever you execute glib-genmarshal one would >>>

Re: hardcode_libdir, rpath and DLLs

2006-04-27 Thread Brian Dessent
Robert Szeleney wrote: > Unfortunately, PE DLLs don't support this --rpath option. Is there any > way to tell libtool to use something different for this? > > Probably using LD_LIBRARY_PATH. Though I think that this will not > really work, because whenever you execute glib-genmarshal one would >

hardcode_libdir, rpath and DLLs

2006-04-27 Thread Robert Szeleney
Hi! If I understand the libtool concept correctly, libtool passes -rpath to the linker when building an executable which depends on a not yet installed library. For instance, when building glib, glib-2.0.0.dll is built at first. When building glib-genmarshal, libtool passes -Wl,--rpath,/path_to_n