From: Matt Fleming <matt@console-pimps.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Darren Hart <dvhart@linux.intel.com>,
Matt Fleming <matt.fleming@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] recipes-devtools: Add OVMF recipe
Date: Tue, 12 Aug 2014 20:05:29 +0100 [thread overview]
Message-ID: <20140812190529.GK15082@console-pimps.org> (raw)
In-Reply-To: <20140812155138.GR14848@jama>
On Tue, 12 Aug, at 05:51:38PM, Martin Jansa wrote:
>
> I don't think we have iasl in oe-core.
Oops, my bad. I thought I'd checked that but turns out I was looking in
the wrong tree.
I'll include the iasl recipe with the next submission.
> Also the styleguide says you should use space around = (SRCREV, DEPENDS,
> COMPATIBLE_HOST, BUILD_OPTIMIZATION, GCC_VER)
Thanks, I'll update the patch.
> > +# OVMF has trouble building with the default optimization of -O2.
> > +BUILD_OPTIMIZATION="-pipe"
> > +
> > +# OVMF supports IA only, although it could conceivably support ARM someday.
> > +COMPATIBLE_HOST='(i.86|x86_64).*'
> > +
> > +do_patch_append() {
> > + bb.build.exec_func('do_fix_iasl', d)
> > + bb.build.exec_func('do_fix_toolchain', d)
>
> Why don't you fix them in do_configure_prepend?
What's the tradeoff?
Though I realise that we're not actually *patching* anything and so
do_configure_prepend() probably does make more semantic sense.
Ah, after a bit of grepping I see that it's a pretty common pattern. OK,
sure, I'll update this.
Thanks for the review.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2014-08-12 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 15:27 [PATCH] recipes-devtools: Add OVMF recipe Matt Fleming
2014-08-12 15:51 ` Martin Jansa
2014-08-12 19:05 ` Matt Fleming [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=20140812190529.GK15082@console-pimps.org \
--to=matt@console-pimps.org \
--cc=dvhart@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=matt.fleming@intel.com \
--cc=openembedded-core@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.