From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/5] binconfig.bbclass: search configs in D instead of S
Date: Tue, 19 Apr 2011 13:10:19 +0200 [thread overview]
Message-ID: <4DAD6D9B.2000909@opendreambox.org> (raw)
In-Reply-To: <1302996215.3122.31.camel@utx.lan>
On 04/17/2011 01:23 AM, Stanislav Brabec wrote:
> Searching for binconfig in S makes more problems than it
> brings benefits. Searching in the installed root seems to be more logical.
>
> Fixes following subtle breakages:
> - binconfig are populated with a different name that upstream intended
> - populated binconfig files that were not intended to be populated
>
> It fixes at least ncurses, which populates ncurses-config instead of
> ncurses5-config and ncursesw5-config, causing secondary breakages.
>
> Signed-off-by: Stanislav Brabec <utx@penguin.cz>
Acked-by: Andreas Oberritter <obi@opendreambox.org>
> diff --git a/classes/binconfig.bbclass b/classes/binconfig.bbclass
> index b3b2236..3d2bf0f 100644
> --- a/classes/binconfig.bbclass
> +++ b/classes/binconfig.bbclass
> @@ -49,7 +49,7 @@ binconfig_package_preprocess () {
> SYSROOT_PREPROCESS_FUNCS += "binconfig_sysroot_preprocess"
>
> binconfig_sysroot_preprocess () {
> - for config in `find ${S} -name '${BINCONFIG_GLOB}'`; do
> + for config in `find ${D} -name '${BINCONFIG_GLOB}'`; do
> configname=`basename $config`
> install -d ${SYSROOT_DESTDIR}${STAGING_BINDIR_CROSS}
> cat $config | sed ${@get_binconfig_mangle(d)} > ${SYSROOT_DESTDIR}${STAGING_BINDIR_CROSS}/$configname
>
next prev parent reply other threads:[~2011-04-19 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 23:23 [PATCH 1/5] binconfig.bbclass: search configs in D instead of S Stanislav Brabec
2011-04-19 11:10 ` Andreas Oberritter [this message]
2011-04-20 10:59 ` Paul Menzel
2011-04-20 11:27 ` Enrico Scholz
2011-04-20 21:44 ` Stanislav Brabec
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=4DAD6D9B.2000909@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.