Re: libtool 1.5 used in serveez package

[Max Bowsher]

Bob Friesenhahn wrote:
> On Sun, 25 May 2003, Max Bowsher wrote:
>
>>> The auto-import feature of GCC will happily import symbols from the DLL.
>>
>> Yes, I know, I was speculating about some kind of
>> hypothetical --dont-export-symbols-from-static-libs flag that could allow
>> DLLs to link with static libs without the danger of them polluting the
DLLs
>> own export namespace. Unfortunately, I don't think there is any to
>> practically do this portably, without things getting horribly messy.
>>
>> What do you think about some mechanism to tell libtool "I know this
>> particular static lib is OK to link with without undesirable side
effects"?
>
> I have little opinion except to note that libtool itself is a big hack
> and adding hacks on top of hacks makes software more difficult to
> understand and more difficult to ensure correct operation.  The hack
> you describe is intended to satisfy platform/solution specific
> requirements.
>
> Maybe the solution is to use a DLL rather than a static library?

My situation is this: I already have some libs installed by the Cygwin
package manager, some of which only have a static version. I don't want to
bother rebuilding these libs as DLLs.

My (horribly hackish) solution is:
lt_cv_deplibs_check_method='file_magic ^x86 archive|^x86 DLL' \
lt_cv_file_magic_cmd='win32_libid' \
./configure

I was thinking how it might be nicer to explicitly specify names of libs to
permit use of, rather than a blanket override of the 'no statics' policy.


Max.