Fails to build. Output:
FAILED: src/libadwaita-1.so.0
Git Clone URL: | https://aur.archlinux.org/libadwaita-without-adwaita-git.git (read-only, click to copy) |
---|---|
Package Base: | libadwaita-without-adwaita-git |
Description: | libadwaita; Includes a patch to not overwrite the system theme |
Upstream URL: | https://gnome.pages.gitlab.gnome.org/libadwaita |
Licenses: | LGPL-2.1-or-later |
Conflicts: | libadwaita |
Provides: | libadwaita, libadwaita-1.so |
Submitter: | ich |
Maintainer: | ich |
Last Packager: | ich |
Votes: | 24 |
Popularity: | 1.78 |
First Submitted: | 2022-04-08 09:57 (UTC) |
Last Updated: | 2024-03-30 14:39 (UTC) |
Fails to build. Output:
FAILED: src/libadwaita-1.so.0
Since latest appstream update to 1.0 that package causes most essential Gnome apps not to work. Requires update, also now fails to build.. It requires libappstream.so.5 not 4.
[164/318] Compiling C object tests/test-about-window.p/test-about-window.c.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Thank you for your effort @ich !
Sorry for not being here for some time, I updated the package version to 1.4.0.
Many thanks to Lukas, who sent me a diff with updated locations via email (also to @mbilbao. Your one works just as well)
@Tim libadwaita 1.4 now requires appstream as a run-time dependency. I updated the PKGBUILD so it should hopefully build for you know.
One way to do this is to copy the gtk-4.0 folder of your theme into the .config folder. Make a script to automate this. This way no need for this package....
@mbilbao For me it still fails to build https://paste.trom.tf/anonoyenos.yaml
@Sam-Burgos Yes you can force all GTK apps to use the system's theme, but you have to do it via the terminal with GTK_THEME=THEME app-name
or via the env file but if you change the system's theme you have to restart your session....very inconvenient..
@Tio : Usually that's the case, you just need to change numbering, as well as the sum (sha256, sha512, other), but there are other cases in which you must check what might have changed (like now)
@mbilbao : I have tested and it seems that only works with version < 1.4, something changed in version 1.4 onwards that doesn't allow me to compile and the tests fail (I have tried even with the latest PKGBUILD from the Arch repositories but compilation fails), so I suggest you that for now, unless that you need something specific from GNOME 45 onwards, use something that might have the latest GTK3, something from GNOME 44 or earlier and/or this library (along with the pinned recommendation given by @ich)
EDIT: You can also use the latest libadwaita from Arch repos and either the recommendation given here or the general GTK option given here, since it seems that so far those still works on theming libadwaita-based apps (once again, also follow the pinned recommendation)
Hey, I made a simple change to PKGBUILD and the diff file. Uploaded to Github if you want to take a look. https://github.com/ManuelBilbao/libadwaita-without-adwaita-git Seems to be working (tried gnome-calculator, gnome-calendar and someone else). The only catch is nautilus, who applies custom themes but looks weird.
This pkg should on official repos. A little hack with significance impact
Pinned Comments
ich commented on 2022-04-08 10:17 (UTC) (edited on 2023-01-10 05:38 (UTC) by ich)
The version of libadwaita provided by this package will use the dconf-variable 'org.gnome.desktop.interface.gtk-theme' to load the theme. This is the same variable that other gtk4-apps (and gnome-tweaks) uses.
For this to work, your theme needs to support gtk4. There may also be some weird formatting until themes are updated to fully support the new widgets; The Arc-family of themes seems to already support most of libadwaita.
Since this replaces the system library, it will only work for apps that actually use it (that is, all apps in the main repo). You will still have to set GTK_THEME if you want to use Flatpaks / Snaps / Appimages
Edit: Please, never just report issues to other gtk projects while using this library. Please always check if the issue persists using extra/libadwaita, and report your issue only on this AUR package if it doesn't.