This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [avail for test] libtool-devel-20030121-1


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
>>>> static
>>>
>>> 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.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]