"Christopher Faylor" cgf@redhat.com wrote:
This fix looks reasonable. I've checked it in with some minor formatting tweaks and a new changelog.
Thank you very much for such a quick response. Could you please also have a look at the .def file parser used by dlltool and probably add support for PRIVATE keyword? Currently statements like the following one:
EXPORTS DllGetClassObject@12=SHELL32_DllGetClassObject@12 @128 PRIVATE
are not handled by dlltool at all.
MSDN: The optional keyword PRIVATE prevents entryname from being placed in the import library generated by LINK. It has no effect on the export in the image also generated by LINK.
Thanks again.