Guidance Request: Correct ANGLE Build Configuration for Unpackaged WinUI 3 Apps

27 views
Skip to first unread message

John Phelan

unread,
Jul 14, 2025, 1:39:45 AMJul 14
to angleproject

Hello ANGLE Team,

First, thank you for all your work on this essential project.

Based on community analysis (see SkiaSharp GitHub Issue #2968), it appears the pre-built ANGLE libraries are incompatible with unpackaged builds (e.g. ones for steam and not for the windows app store). The root cause seems to be that for an unpackaged app to function, the two main ANGLE libraries must be compiled with conflicting build flags:

  • libEGL.dll must be compiled with angle_is_winappsdk=false.

  • libGLESv2.dll must be compiled with angle_is_winappsdk=true.

To make the painpoint as clear as possible, I've created a minimal, fully-automated repository that implements this split-build process that dotnet steam apps seem to have to enact:

GitHub Repository: https://github.com/bytesandwich/unpackagedSkiasharpAngle

The repository's Readme.md contains a detailed analysis of the problem.

Is this split-configuration build the intended or recommended approach for this scenario? Or is there a simpler, officially supported set of gn arguments that achieves the same result without any custom build scripting?

Thank you for your time and for this fantastic project.

Best regards,

Jack

Reply all
Reply to author
Forward
0 new messages