Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

RE: Modules under Cygwin

X-seq: zsh-workers 10835
From: "Andrej Borsenkow" <Andrej.Borsenkow@xxxxxxxxxxxxxx>
To: "Zefram" <zefram@xxxxxxxx>
Subject: RE: Modules under Cygwin
Date: Wed, 19 Apr 2000 18:43:12 +0400
Cc: "ZSH workers mailing list" <zsh-workers@xxxxxxxxxxxxxx>
Importance: Normal
In-reply-to: <E12hvR6-0000Ya-00@xxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm

>
> Andrej Borsenkow wrote:
> >The import library is a regular UNIX-like .a library, but it only
> >contains the tiny bit of information needed to tell the OS how your
> >program interacts with ("imports") the dll. This information
> is linked
> >into your .exe. This is also generated by dlltool.
>
> This is a "stub library" in the terminology I've seen under Unix.
> This is needed when linking (at compile time) against a shared library
> (as we do with libzsh), but is *not* relevant to the modules
> themselves.
> There we need dynamic symbol lookup (dlsym()).
>

Yes, of course. But, if I can believe Cygwin manual, we have to generate
this stub library from real dll and link against it. To do this we need
either thousand -L's or we can drop all generated stubs in a single
directory. Just a simplification (I hope) of makefile.

-andrej

References:
- Re: Modules under Cygwin
  - From: Zefram

Messages sorted by: Reverse Date, Date, Thread, Author