On Tue, 14 Sep 2004, Maarten Boekhold wrote:
Bob Friesenhahn wrote:
My understanding is that for non-module DLLs, the .dll file is installed
in the bin directory so it is likely to be in the user's path. If the
Then how does libtool decide whether a DLL is a (non)-module? The --module
flag? (l
Bob Friesenhahn wrote:
> On Tue, 14 Sep 2004, Maarten Boekhold wrote:
>> The Makefile.am's for these plugins are all more or less the same.
>> Yet, some plugins get installed as '$(libdir)/bin/cygX.dll', some
>> as '$(libdir)/modules/cygX.dll', and others as
>> '$(libdir)/modules/lib.
Bob Friesenhahn wrote:
My understanding is that for non-module DLLs, the .dll file is installed
in the bin directory so it is likely to be in the user's path. If the
Then how does libtool decide whether a DLL is a (non)-module? The
--module flag? (looking through the sources... yes, those libs
On Tue, 14 Sep 2004, Maarten Boekhold wrote:
Hi all,
I'm a little confused about how libtool (or maybe it's automake) behaves when
used as 'libtool --mode=install' for a shared library *under cygwin*.
I am in the process of porting XFCE (http://www.xfce.org) to cygwin/X. XFCE
has various subpack
Hi all,
I'm a little confused about how libtool (or maybe it's automake) behaves
when used as 'libtool --mode=install' for a shared library *under cygwin*.
I am in the process of porting XFCE (http://www.xfce.org) to cygwin/X.
XFCE has various subpackages, and a number of them use a plugin
mech
