Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <39AFB333.69CE5F95@ece.gatech.edu> Date: Fri, 01 Sep 2000 09:46:28 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Tor Lillqvist CC: cygwin AT sources DOT redhat DOT com Subject: Re: DLL naming conventions References: <200009011148 DOT OAA23769 AT urkki DOT tellabs DOT fi> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Tor Lillqvist wrote: > > "Charles S. Wilson" 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 AT sourceware DOT cygnus DOT com