This is the mail archive of the
mailing list for the Cygwin project.
Re: [avail for test] libtool-devel-20030121-1
- From: "Max Bowsher" <maxb at ukf dot net>
- To: "Charles Wilson" <cwilson at ece dot gatech dot edu>,"Ralf Habacker" <Ralf dot Habacker at freenet dot de>
- Cc: "cygwin" <cygwin at cygwin dot com>
- Date: Sun, 16 Feb 2003 22:16:01 -0000
- Subject: Re: [avail for test] libtool-devel-20030121-1
- References: <001201c2d5c2$68cd4550$755f07d5@BRAMSCHE> <3E500500.firstname.lastname@example.org>
Charles Wilson wrote:
>> Ralf Habacker wrote:
>>>>> BTW: Do you know which libraries are also hybrid execpt of
>>>>> cygwin1.dll ?
>>>> There are about a half-dozen in /usr/lib/w32api -- and worse, the
>>> members are "bad" variable types; if you make the static members
>>> part of the DLL, then these vars can't be auto-imported without
>>> using pseudo-relocs. Of course, since the DLLs are provided by MS,
>>> we can't really modify what is in them.
>>> Thats very bad.
>> Yeah. I don't know why these implibs need to declare these static
>> structures; it's possible that w32api is just following the lead of
>> the corresponding .lib files in the MSVC distribution.
>> But, that's neither here nor there. IF these crossbreed implibs are
libuuid.a at least is static *only* - not crossbreed. So there really is no
way for libtool know to allow it except by name.
>> detected as "import libraries" then libtool will let you link a
>> sharedlib using them as dependencies.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html