There is no MinGW (mingwX64) artifact for Decompose Router, so Kotlin/Native code targeting Windows cannot use RouterContext.
Concrete case: the Windows host view models in NYTimes-KMP (:app:windows, consumed by WPF / WinUI / MAUI through kotlin-native-nuget) have to own lifecycle directly, while the Compose and iOS hosts restore route state through Decompose Router adapters.
Adding mingwX64() to the published targets would let the Windows hosts share the same router-driven navigation and state restoration.
There is no MinGW (
mingwX64) artifact for Decompose Router, so Kotlin/Native code targeting Windows cannot useRouterContext.Concrete case: the Windows host view models in NYTimes-KMP (
:app:windows, consumed by WPF / WinUI / MAUI through kotlin-native-nuget) have to own lifecycle directly, while the Compose and iOS hosts restore route state through Decompose Router adapters.Adding
mingwX64()to the published targets would let the Windows hosts share the same router-driven navigation and state restoration.