From: James Knight <git@jdknight.me>
To: buildroot@buildroot.org
Cc: James Knight <git@jdknight.me>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: [Buildroot] [PATCH 2/3] package/libgtk4: remove schema compile hook
Date: Fri, 8 Aug 2025 23:37:56 -0400 [thread overview]
Message-ID: <20250809033757.1197-2-git@jdknight.me> (raw)
In-Reply-To: <20250809033757.1197-1-git@jdknight.me>
Dropping the need for this package to compile any schemas as the
libglib2 package (a dependency) already handles this during target
finalization.
Signed-off-by: James Knight <git@jdknight.me>
---
package/libgtk4/libgtk4.mk | 6 ------
1 file changed, 6 deletions(-)
diff --git a/package/libgtk4/libgtk4.mk b/package/libgtk4/libgtk4.mk
index b00a2facad..f63e320629 100644
--- a/package/libgtk4/libgtk4.mk
+++ b/package/libgtk4/libgtk4.mk
@@ -79,12 +79,6 @@ else
LIBGTK4_CONF_OPTS += -Dbuild-demos=false -Dbuild-examples=false
endif
-define LIBGTK4_COMPILE_GLIB_SCHEMAS
- $(HOST_DIR)/bin/glib-compile-schemas \
- $(TARGET_DIR)/usr/share/glib-2.0/schemas
-endef
-LIBGTK4_POST_INSTALL_TARGET_HOOKS += LIBGTK4_COMPILE_GLIB_SCHEMAS
-
# here, we build a native gtk4-update-icon-cache as host-libgtk4
HOST_LIBGTK4_DEPENDENCIES = \
--
2.49.0.windows.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-09 3:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 3:37 [Buildroot] [PATCH 1/3] package/libgtk3: remove schema compile hook James Knight
2025-08-09 3:37 ` James Knight [this message]
2026-01-19 10:09 ` [Buildroot] [PATCH 2/3] package/libgtk4: " Arnout Vandecappelle via buildroot
2025-08-09 3:37 ` [Buildroot] [PATCH 3/3] package/gvfs: remove schema compile and cleanup hook James Knight
2026-01-19 10:08 ` Arnout Vandecappelle via buildroot
2026-01-06 22:03 ` [Buildroot] [PATCH 1/3] package/libgtk3: remove schema compile hook Thomas Petazzoni via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250809033757.1197-2-git@jdknight.me \
--to=git@jdknight.me \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox