You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moved from Azure Boards. Original creation timestamp: 2022-01-02 21:00 +05:30.
Today, to consume OneToolkit WinRT APIs from C++/WinRT, you've to manually include the generated projection headers. Previously the OneToolkit.h header file included all of them, however, now I'm considering moving away from headers and using modules instead. The problem is that C++/WinRT doesn't yet support consuming projection headers as a module, and since it defines macros, causes too many warnings when you try to export them from a module. Find a way to consume those APIs defined in projection headers directly by importing the module.
The text was updated successfully, but these errors were encountered:
Moved from Azure Boards. Original creation timestamp: 2022-01-02 21:00 +05:30.
Today, to consume OneToolkit WinRT APIs from C++/WinRT, you've to manually include the generated projection headers. Previously the OneToolkit.h header file included all of them, however, now I'm considering moving away from headers and using modules instead. The problem is that C++/WinRT doesn't yet support consuming projection headers as a module, and since it defines macros, causes too many warnings when you try to export them from a module. Find a way to consume those APIs defined in projection headers directly by importing the module.
The text was updated successfully, but these errors were encountered: