-
Notifications
You must be signed in to change notification settings - Fork 56
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
Types with duplicated names across multiple namespaces do not map #181
Comments
@amerkoleci FYI this is a blocker for Vortice 2.0 migration. |
Right, when I added WinUI bindings i had to manually wrap those types as the namespace was ignored and only the name was considered |
Yeah. After a brief investigation, that's actually headers fault. :) Workaround is to split into multiple assemblies. |
I started new Vortice.WinUI but types doesn't get generated even in new assembly, my Vortice.WinUI depends on Vortice.DXGI which blocks the WinUI types generations cause ISwapChainBackgroundPanelNative_INTERFACE_DEFINED etc. How can I workaround this? |
I've tried to workaround by modifying the header with: Adding the WINUI but it doesn't work as well |
I've had to add manually all code with just GUID changed: amerkoleci/Vortice.Windows@1b769b6 |
Feels like we have a type deduplication malfunctioning. Some rogue HashSet comparator? Vortice.DXGI.WinUI for reference.
Does not generate
IVirtualSurfaceImageSourceNative
and the rest that are duplicated across these headers. TODO: Investigate for 2.0.The text was updated successfully, but these errors were encountered: