adw_init causes g_settings_schema_source_lookup: assertion 'source != NULL' failed due to missing glib schema file on Windows / MacOS

[Clemapfel]

Calling adw_init using the libadwaita_jll causes the following error message:

using libadwaita_jll
ccall(("adw_init", libadwaita_jll.libadwaita), Cvoid, ())

(process:10512): GLib-GIO-CRITICAL **: 15:29:41.923: g_settings_schema_source_lookup: assertion 'source != NULL' failed

This is only the case for Windows and MacOS.

I investigated this and the reason is a missing schema file in the Glib_jll on those platforms.

The solution would be to add a build step to the Glib_jll build_tarballs.jl that downloads the following files:

• https://gitlab.gnome.org/GNOME/gtk/-/raw/main/gtk/org.gtk.gtk4.Settings.ColorChooser.gschema.xml?inline=false
• https://gitlab.gnome.org/GNOME/gtk/-/raw/main/gtk/org.gtk.gtk4.Settings.Debug.gschema.xml?inline=false
• https://gitlab.gnome.org/GNOME/gtk/-/raw/main/gtk/org.gtk.gtk4.Settings.EmojiChooser.gschema.xml?inline=false
• https://gitlab.gnome.org/GNOME/gtk/-/raw/main/gtk/org.gtk.gtk4.Settings.FileChooser.gschema.xml?inline=false

Places them in \share\glib-2.0\schema, then uses the aready available glib-compile-schema executable in the glibs /bin directory to compile the above files into gschemas.compiled, which should be placed in glib-2.0/schemas

I tried this solution which was suggested here on windows and it does work, though I modified the already installed artifact folder, which is not a feasible fix. This should happen during the GLib_jll build step, which requires modification of the binary builder script, it should only be a few lines.

Would it be possible to modify the glib and libadwaita jlls to address this? If not, where would I submit a pull request for this? I think you guys are doing the gnome jlls so I'm unsure of where to ask except here.

[jwahlstrand]

I have been updating the jll's but would be thrilled to have help getting them working better. Issues about jll's are usually filed at https://github.com/JuliaPackaging/Yggdrasil and that's where you would submit a PR to modify the Glib_jll build.

[jwahlstrand]

I plan to update the Glib_jll version for my own reasons and just looked at this request in detail. It's not typical to copy over files from other libraries during a build, and I would like to humbly suggest a different solution.

In Gtk.jl and Gtk4.jl, the environmental variable XDG_DATA_DIRS is set in __init__() to include artifact directories with schemas and icons: https://github.com/JuliaGtk/Gtk4.jl/blob/1c80984c1bc50bd2fd425439891ca827a278483c/src/Gtk4.jl#L123C5-L129C38

On Linux this does have side effects: see JuliaGraphics/Gtk.jl#647. But perhaps you could adopt this approach on Windows and Mac? If I understand things correctly, the reason you don't see those errors on Linux is because the schemas are already installed in a standard directory like /usr/share/glib-2.0/schemas (which assumes that Linux users have GTK4 installed through their distribution).