www.delorie.com/archives/browse.cgi | search |
Charles Wilson wrote: > ... > You probably *should* use def files if (a) you're developing a library > that other folks might want to use, without recompiling their > application code, and (b) you want to support those apps that > 'import-by-number' from the dll. With the no-def-file method, you're > never guaranteed that the name/numbers will be the same from build to > build. I understand what you are saying, but if developers are using my headers and my import library to link with my DLL, wouldn't they always be importing by name? I don't know anything about the import by number method. Why is it ever used? How is it used? More info, please... Anyway, I hope at least the information in my message about the alternate way to build DLLs helped you. > --Chuck Carl Thompson > ... -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |