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
The latest release of GtkSharp has some issues on macOS/arm64 (M1). This issue tracks the issues: found / fixed / released affecting this configuration.
MartinZikmund
added
difficulty/medium 🤔
Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI
platform/gtk
Categorizes an issue or PR as relevant to GTK
and removed
difficulty/tbd
Categorizes an issue for which the difficulty level needs to be defined.
labels
Jul 24, 2023
MartinZikmund
changed the title
[macos][arm64] Tracking GtkSharp issues affecting Skia/Gtk
[Epic] [macos][arm64] Tracking GtkSharp issues affecting Skia/Gtk
Jul 24, 2023
@MartinZikmund no, I would left it open for reference. My fixes are merged but they were never released so the issues remain (unless you build gtk# yourself).
Current behavior
The latest release of GtkSharp has some issues on macOS/arm64 (M1). This issue tracks the issues: found / fixed / released affecting this configuration.
This affects application startup (native libraries can't be found)
g_filename_[from|to]_utf8
signatures for 64 bits platforms GtkSharp/GtkSharp#346This affects native file dialogs
Expected behavior
An Uno app running on Skia/Gtk on an arm64-based Mac should behave identically as running on x86_64 Mac computer.
How to reproduce it (as minimally and precisely as possible)
Run Uno Skia/Gtk apps on an arm64-based Mac.
Workaround
Use the HEAD of the
develop
branch ofGtkSharp
.Works on UWP/WinUI
No response
Environment
Uno.UI / Uno.UI.WebAssembly / Uno.UI.Skia
NuGet package version(s)
No response
Affected platforms
Skia (GTK on Linux/macOS/Windows)
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
Some issues could also exists on other arm64 platforms (linux or windows).
The text was updated successfully, but these errors were encountered: