<div dir="ltr">On Thu, Jul 17, 2008 at 7:48 PM, Philip Lowman <<a href="mailto:philip@yhbt.com">philip@yhbt.com</a>> wrote:<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">Does anyone know of any other platforms that share filename extensions for archive vs. shared libraries other than MSVC/Win32?</div></blockquote><div><br>The .lib files associated with DLLs on Windows are not really "shared libraries". The DLLs themselves are the shared libraries. The .lib files are just directives to the linker that say how to resolve to the DLL. They are sort of mini-archives with a bunch of "function pointers," if you will, in them instead of object code. The object code is in the DLL and the .lib file points to it.<br>
<br>The .lib tells the linker that when it links a program against any "functions" in it, that the built executable must be able to load the corresponding DLL when it loads to resolve those functions.<br><br>Having said all this, yeah, it's not pretty..., but it's the way it is because of the way it was...<br>
<br>And I am not aware of any other platforms that share filename extensions for archive vs. shared libraries.<br><br><br>;)<br>David<br><br></div></div></div>