driver1998

既然是WinUI 3那可以考虑上Uno？应该会比拿Avalonia重写更容易一点。

> @SA-Root When using h264_mf encoder, it seems to be using CPU to encode the video. You need to pass additional flags to make hardware encoding work with the ffmpeg...

I am designing various dialogs in NanaZip. These are early XAML mockups, subject to change. We are still going to use System XAML Islands via Mile.Xaml for the final UI.

Can you just rename mingw32-make as nmake? Simple makefiles are generally compatible across different make implementations. What makes nmake makefiles special is that it usually assumes you use CMD instead...

Then what you need is msbuild instead of nmake. msbuild is open source though.

I am trying to cross compile to Windows ARM64 on x86_64 host, and hit the same issue. A build flag to disable dict generation would be great, we build for...

.NET Framework AnyCPU 程序只要在项目设置里允许ARM64就可以在Windows 11上原生运行，现在VS有个一键开关： https://devblogs.microsoft.com/visualstudio/how-to-run-net-apps-natively-on-arm64-devices/ 我记得之前WeaselSetup依赖了RIME的库，如果没打算编译ARM64的RIME的话保持WeaselSetup x86（32位或64位）是最好的。 Win10只支持32位x86的.NET。

> 这么看来 .NET Framework 可能还不太适合干这个工作？ Windows 10 和老版本的 11 确实没有好的办法原生运行 (使用AnyCPU的话)，但原来 C++ 的 WeaselSetup 也是模拟运行的，所以没差

Right now, this works with `GeneratedComInterface`s: ```csharp var cw = new StrategyBasedComWrappers(); var unknownPtr = MarshalInspectable.FromManaged(someObj); var someInterfaceObj = (ISomeInterface)cw.GetOrCreateObjectForComInstance(unknownPtr, CreateObjectFlags.None); ```

I did a Windows ARM build way back and don't recall it needed special treatment. (libass required a patch to disable x86 ASM but that is now unnecessary) https://github.com/driver1998/Aegisub