From: Adrian Perez de Castro <aperez@igalia.com>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Thomas Devoogdt <thomas.devoogdt@barco.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v5 5/5] package/libgtk3: fix update-icon-cache on empty directory
Date: Mon, 24 Apr 2023 15:14:39 +0300 [thread overview]
Message-ID: <20230424151439.GJ3960430@igalia.com> (raw)
In-Reply-To: <20230227105838.358916-5-thomas.devoogdt@barco.com>
[-- Attachment #1.1: Type: text/plain, Size: 1472 bytes --]
On Mon, 27 Feb 2023 11:58:38 +0100 Thomas Devoogdt <thomas@devoogdt.com> wrote:
> If both, hicolor-icon-theme (selected by libgtk3-demo) and
> adwaita-icon-theme is not selected, then the /usr/share/icons
> folder is empty, causing find to fail.
>
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
Tested-by: Adrian Perez de Castro <aperez@igalia.com>
> ---
> v5:
> - Fixed indentation.
> - Grouped patches.
> ---
> package/libgtk3/libgtk3.mk | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/package/libgtk3/libgtk3.mk b/package/libgtk3/libgtk3.mk
> index 2821c7eb52..191e28dda6 100644
> --- a/package/libgtk3/libgtk3.mk
> +++ b/package/libgtk3/libgtk3.mk
> @@ -146,8 +146,9 @@ endef
> # Create icon-theme.cache for each of the icon directories/themes
> # It's not strictly necessary but speeds up lookups
> define LIBGTK3_UPDATE_ICON_CACHE
> - find $(TARGET_DIR)/usr/share/icons -maxdepth 1 -mindepth 1 -type d \
> - -exec $(HOST_DIR)/bin/gtk-update-icon-cache {} \;
> + [ ! -d $(TARGET_DIR)/usr/share/icons ] || \
> + find $(TARGET_DIR)/usr/share/icons -maxdepth 1 -mindepth 1 -type d \
> + -exec $(HOST_DIR)/bin/gtk-update-icon-cache {} \;
> endef
> LIBGTK3_TARGET_FINALIZE_HOOKS += LIBGTK3_UPDATE_ICON_CACHE
>
> --
> 2.39.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
>
Cheers,
—Adrián
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-04-24 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:58 [Buildroot] [PATCH v5 1/5] package/at-spi2-core: bump to version 2.47.1 Thomas Devoogdt
2023-02-27 10:58 ` [Buildroot] [PATCH v5 2/5] package/at-spi2-atk: remove package Thomas Devoogdt
2023-04-24 12:13 ` Adrian Perez de Castro
2023-02-27 10:58 ` [Buildroot] [PATCH v5 3/5] package/atk: " Thomas Devoogdt
2023-04-15 15:37 ` Yann E. MORIN
2023-04-21 9:55 ` Adrian Perez de Castro
2023-04-24 12:13 ` Adrian Perez de Castro
2023-02-27 10:58 ` [Buildroot] [PATCH v5 4/5] package/libgtk3: re-enable atk-bridge Thomas Devoogdt
2023-04-24 12:14 ` Adrian Perez de Castro
2023-02-27 10:58 ` [Buildroot] [PATCH v5 5/5] package/libgtk3: fix update-icon-cache on empty directory Thomas Devoogdt
2023-04-24 12:14 ` Adrian Perez de Castro [this message]
2023-06-08 20:52 ` Peter Korsgaard
2023-04-24 12:11 ` [Buildroot] [PATCH v5 1/5] package/at-spi2-core: bump to version 2.47.1 Adrian Perez de Castro
2023-04-25 14:30 ` Adrian Perez de Castro
2023-04-27 14:41 ` Adrian Perez de Castro
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=20230424151439.GJ3960430@igalia.com \
--to=aperez@igalia.com \
--cc=buildroot@buildroot.org \
--cc=thomas.devoogdt@barco.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.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