From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] lmbench: if a machine config file exists, install it
Date: Fri, 22 Aug 2014 23:09:34 +0200 [thread overview]
Message-ID: <20140822210934.GE20524@jama> (raw)
In-Reply-To: <CABcZANn26XQ2GP7V_=vyT3jH7mLTC8c688uwvpjW9=LCGKRVZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
On Fri, Aug 22, 2014 at 01:16:03PM -0700, Christopher Larson wrote:
> On Tue, Aug 19, 2014 at 5:07 AM, Martin Jansa <martin.jansa@gmail.com>
> wrote:
>
> > On Tue, Aug 19, 2014 at 04:49:24PM +0500, Yasir-Khan wrote:
> > > Signed-off-by: Christopher Larson <chris_larson@mentor.com>
> > > Signed-off-by: Yasir-Khan <yasir_khan@mentor.com>
> > > ---
> > > .../recipes-benchmark/lmbench/lmbench_3.0-a9.bb | 7 +++++++
> > > 1 file changed, 7 insertions(+)
> > >
> > > diff --git a/meta-oe/recipes-benchmark/lmbench/lmbench_3.0-a9.bb
> > b/meta-oe/recipes-benchmark/lmbench/lmbench_3.0-a9.bb
> > > index 41db150..a3873a6 100644
> > > --- a/meta-oe/recipes-benchmark/lmbench/lmbench_3.0-a9.bb
> > > +++ b/meta-oe/recipes-benchmark/lmbench/lmbench_3.0-a9.bb
> > > @@ -60,6 +60,13 @@ do_install () {
> > > ${D}${bindir}/lmbench-run
> > > install -m 0755 ${S}/scripts/lmbench ${D}${bindir}
> > > install -m 0755 ${S}/scripts/* ${D}${datadir}/lmbench/scripts
> > > +
> > > + # If the machine installs a config file, install it to the
> > appropriate place
> > > + if [ -f ${WORKDIR}/CONFIG.${MACHINE} ]; then
> > > + install -D 0644 ${WORKDIR}/CONFIG.${MACHINE} \
> > > + ${D}/${datadir}/lmbench
> > /bin/${TARGET_PREFIX}/CONFIG.${MACHINE}
> > > + fi
> >
> > that makes lmbench MACHINE_ARCH and PACKAGE_ARCH isn't set that way.
>
>
>
> Any objection to creating an lmbench-config package, either in lmbench or
> in its own recipe, making that machine specific, and rrecommending it from
> lmbench? IIRC that's how we usually handle such things (e.g. alsa-state
> pulls in alsa-states which is usually empty, but which bsps can append to
> pull in the machine specific configuration).
I'm fine with separate recipe, rdepended from main one and excluded with
SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-08-22 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 11:49 [meta-oe][PATCH] lmbench: if a machine config file exists, install it Yasir-Khan
2014-08-19 12:07 ` Martin Jansa
2014-08-22 20:16 ` Christopher Larson
2014-08-22 21:09 ` Martin Jansa [this message]
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=20140822210934.GE20524@jama \
--to=martin.jansa@gmail.com \
--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.