From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] divine: fix divine-config
Date: Fri, 4 Jan 2013 17:31:16 +0100 [thread overview]
Message-ID: <20130104173116.222de178@skate> (raw)
In-Reply-To: <50E6BFE2.2090405@zacarias.com.ar>
Dear Gustavo Zacarias,
On Fri, 04 Jan 2013 08:41:22 -0300, Gustavo Zacarias wrote:
> On 01/03/2013 07:09 PM, Stefan Fr?berg wrote:
>
> > +define DIVINE_STAGING_DIVINE_CONFIG_FIXUP
> > + $(SED) "s,^prefix=.*,prefix=\'$(STAGING_DIR)/usr\',g" $(STAGING_DIR)/usr/bin/divine-config
> > + $(SED) "s,^exec_prefix=.*,exec_prefix=\'$(STAGING_DIR)/usr\',g" $(STAGING_DIR)/usr/bin/divine-config
> > +endef
> > +
> > +DIVINE_POST_INSTALL_STAGING_HOOKS += DIVINE_STAGING_DIVINE_CONFIG_FIXUP
> > +
>
> This could be handled in a generic way for all the packages that ship a
> *-config file.
> Something like:
>
> DIVINE_CONFIG_FIXUP = divine-config
>
> And then do the generic sed magic in package/pkg-generic.mk
> How about that?
Sounds ok, but instead:
DIVINE_CONFIG_FIXUP = $(STAGING_DIR)/usr/bin/divine-config
And also need to support multiple files being passed.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-04 16:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 22:09 [Buildroot] [PATCH] divine: fix divine-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] giblib: fix giblib-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] imlib2: fix imlib2-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] libgcrypt: fix libgcrypt-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] imagemagick: fix Magick[++|Core|Wand]-config Stefan Fröberg
2013-01-04 21:45 ` Peter Korsgaard
2013-01-03 22:09 ` [Buildroot] [PATCH] neon: fix neon-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] libnspr: fix nspr-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] xlib_libXft: fix xft-config Stefan Fröberg
2013-01-04 23:30 ` Peter Korsgaard
2013-01-05 13:33 ` Stefan Fröberg
2013-01-04 11:41 ` [Buildroot] [PATCH] divine: fix divine-config Gustavo Zacarias
2013-01-04 14:17 ` Samuel Martin
2013-01-04 14:29 ` Gustavo Zacarias
2013-01-04 14:56 ` Stefan Fröberg
2013-01-04 15:00 ` Gustavo Zacarias
2013-01-06 5:41 ` Baruch Siach
2013-01-06 8:27 ` Samuel Martin
2013-01-06 8:34 ` Baruch Siach
2013-01-06 12:39 ` Thomas Petazzoni
2013-01-06 14:15 ` Stefan Fröberg
2013-01-06 18:12 ` Stefan Fröberg
2013-01-07 22:17 ` Arnout Vandecappelle
2013-01-07 22:35 ` Stefan Fröberg
2013-01-08 7:48 ` Arnout Vandecappelle
2013-01-08 8:10 ` Thomas Petazzoni
2013-01-08 8:24 ` Arnout Vandecappelle
2013-01-04 16:29 ` Thomas Petazzoni
2013-01-04 16:31 ` Thomas Petazzoni [this message]
2013-01-04 17:10 ` Gustavo Zacarias
2013-01-04 17:13 ` Stefan Fröberg
2013-01-04 21:49 ` Peter Korsgaard
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=20130104173116.222de178@skate \
--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