From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] gdk-pixbuf: copy loaders.cache later on
Date: Thu, 23 Feb 2017 22:22:56 +0100 [thread overview]
Message-ID: <20170223222256.56f506fe@free-electrons.com> (raw)
In-Reply-To: <20170223194448.3785-1-gustavo@zacarias.com.ar>
Hello,
On Thu, 23 Feb 2017 16:44:48 -0300, Gustavo Zacarias wrote:
> Trying to copy loaders.cache from host-gdk-pixbuf to the gdk-pixbuf
> build directory in the post-patch hook is too early when using TLP (it
> breaks horribly) since host-gdk-pixbuf isn't built yet during the
> massive unpack/patch cycle.
> Switch it to the pre-build hook instead which ensures that gdk-pixbuf
> dependencies were already built.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Since the first pat
> ---
> package/gdk-pixbuf/gdk-pixbuf.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/gdk-pixbuf/gdk-pixbuf.mk b/package/gdk-pixbuf/gdk-pixbuf.mk
> index e4d3658..0f4eeb1 100644
> --- a/package/gdk-pixbuf/gdk-pixbuf.mk
> +++ b/package/gdk-pixbuf/gdk-pixbuf.mk
> @@ -80,7 +80,7 @@ define GDK_PIXBUF_COPY_LOADERS_CACHE
> cp -f $(HOST_DIR)/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache \
> $(@D)/gdk-pixbuf
> endef
> -GDK_PIXBUF_POST_PATCH_HOOKS += GDK_PIXBUF_COPY_LOADERS_CACHE
> +GDK_PIXBUF_PRE_BUILD_HOOKS += GDK_PIXBUF_COPY_LOADERS_CACHE
>
> $(eval $(autotools-package))
> $(eval $(host-autotools-package))
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-23 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 19:44 [Buildroot] [PATCH next] gdk-pixbuf: copy loaders.cache later on Gustavo Zacarias
2017-02-23 21:22 ` Thomas Petazzoni [this message]
2017-02-23 21:31 ` Thomas Petazzoni
2017-02-23 21:23 ` Thomas Petazzoni
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=20170223222256.56f506fe@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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