This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: DLL naming conventions
- To: Tor Lillqvist <tml at iki dot fi>
- Subject: Re: DLL naming conventions
- From: "Charles S. Wilson" <cwilson at ece dot gatech dot edu>
- Date: Fri, 01 Sep 2000 09:46:28 -0400
- CC: cygwin at sources dot redhat dot com
- References: <200009011148.OAA23769@urkki.tellabs.fi>
Tor Lillqvist wrote:
>
> "Charles S. Wilson" <cwilson@ece.gatech.edu> writes:
>
> > 2) on interface (API/ABI) versioning
> > http://www.gnu.org/software/libtool/manual.html#Versioning
>
> Note that this document talks about stuff that AFAIK requires
> cooperation from the runtime dynamic linker, that it knows how to
> search for a suitable version of a shared library. No such dynamic
> linker on Win32, alas.
>
> (Writing a Unix-like (or should one say ELF-like?) dynamic linker for
> Win32 would be an interesting exercise, of course.)
!!!! ????
There is *something* in the windows system that gets notified that
myapp.exe depends on mydll.dll whenever you execute myapp.exe. This
*something* searches the file system according to the search path
described earlier in this thread, loads the dll into the executable
process's memeory space (rebasing the memory location if necessary), and
fixes up all the internal pointers to match the in-process virtual
memory location.
Isn't that considered a dynamic linker? (Whether you call that
*something* a dynamic linker or not is really immaterial. The
*something* is a runtime loader, and that's what the reference above is
discussing)
--Chuck
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com