-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The API "Gdi32" is ambiguous #1201
Comments
This is because gdi32.dll contains methods that are expressed both in the "SDK" and the "WDK". I think we'll just fix this by generating from both. |
In the meantime, the workaround would be to ask for the specific functions you need. That's the recommended approach anyway since it will result in far less code generated, and less bloat in your dll. |
Thank you very much for your reply. for someone like me who is lazy, sometimes I want to produce all the methods at once so that I can easily retrieve a method, even if I only remember the approximate name. Otherwise, I have to search for the Win32 API ,try to copy and paste the complete method name, which feels very inconvenient. Another area of confusion is why this issue occurs in higher versions and not in lower versions? |
Lower versions used older metadata and (if you go back far enough) didn't include the WDK metadata at all. So the ambiguity is introduced when you have more metadata that describes more functions. |
NativeMethods.txt
User32.*
Gdi32.*
DwmAPI.*
Kernel32.*
WM_*
SC_*
S_*
CW_*
MSGFLTINFO_*
my config above but second line Gdi32.* trigger exception :The API "Gdi32" is ambiguous
how could i fix it,anyone can help?
The text was updated successfully, but these errors were encountered: