Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "Wold, Saul" <saul.wold@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v4 7/7] image_types_wic: schedule prepare_wic_build correctly
Date: Mon, 22 May 2017 10:19:35 +0300	[thread overview]
Message-ID: <20170522071935.GA11250@linux.intel.com> (raw)
In-Reply-To: <1495234544.16942.222.camel@intel.com>

On Fri, May 19, 2017 at 10:55:46PM +0000, Wold, Saul wrote:
> On Wed, 2017-05-17 at 13:47 +0000, Ed Bartosh wrote:
> > Scheduled prepare_wic_build only if wic build enabled.
> > Added dependencies to kernel and efi bootloader deploy
> > tasks only if EFI is enabled.
> > 
> > This should fix build failure on machines without
> > EFI functionality.
> > 
> > Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> > ---
> >  meta/classes/image_types_wic.bbclass | 27 ++++++++++++++----------
> > ---
> >  1 file changed, 14 insertions(+), 13 deletions(-)
> > 
> > diff --git a/meta/classes/image_types_wic.bbclass
> > b/meta/classes/image_types_wic.bbclass
> > index d8430e49ac..3b73261d5e 100644
> > --- a/meta/classes/image_types_wic.bbclass
> > +++ b/meta/classes/image_types_wic.bbclass
> > @@ -69,6 +69,11 @@ python () {
> >                  # file in process_wks_template as well, so just put
> > it in
> >                  # a variable and let the metadata deal with the
> > deps.
> >                  d.setVar('_WKS_TEMPLATE', body)
> > +
> > +        bb.build.addtask('do_prepare_wic_build', 'do_image_wic',
> > None, d)
> > +        if d.getVar('EFI_CLASS'):
> > +            d.appendVarFlag('do_prepare_wic_build', 'depends',
> > +                            '%s%s:do_deploy 
> > virtual/kernel:do_deploy' % (d.getVar('MLPREFIX'),
> > d.getVar('EFI_CLASS')))
> 
> Ed, 
> Have you tested this with any layers?
I tested it with poky layers as I do for all my patches.

> I tied recently with meta-
> intel and tripped over an issue with the rmc-boot not having an actual
> target for the EFI_CLASS to have a deploy task caused a failure.

I also tested it on qemuarm machine that doesn't support EFI. It worked just fine.

I'll try to test it with meta-intel. Can you provide more detailed
instructions how to reproduce this issue? Which image did you try to
build?

--
Regards,
Ed


  reply	other threads:[~2017-05-22  7:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 13:47 [PATCH v4 0/7] i#10073: generic EFI for wic Ed Bartosh
2017-05-17 13:47 ` [PATCH v4 1/7] systemd-boot: create output dir if it doesn't exist Ed Bartosh
2017-05-17 13:47 ` [PATCH v4 2/7] efi: add efi_bootfs_populate API Ed Bartosh
2017-05-17 13:47 ` [PATCH v4 3/7] image_types_wic: add do_populate_bootfs task Ed Bartosh
2017-05-17 13:47 ` [PATCH v4 4/7] image_types_wic: merged 2 tasks Ed Bartosh
2017-05-17 13:47 ` [PATCH v4 5/7] oe-selftest: add wic tests for generic EFI Ed Bartosh
2017-05-17 13:47 ` [PATCH v4 6/7] grub-efi: fixed default value of GRUB_ROOT Ed Bartosh
2017-05-17 13:47 ` [PATCH v4 7/7] image_types_wic: schedule prepare_wic_build correctly Ed Bartosh
2017-05-19 22:55   ` Wold, Saul
2017-05-22  7:19     ` Ed Bartosh [this message]
2017-05-23 16:35       ` Burton, Ross
2017-06-01 15:21 ` [PATCH v4 0/7] i#10073: generic EFI for wic Wold, Saul
2017-06-09 11:13   ` Ed Bartosh

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=20170522071935.GA11250@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=saul.wold@intel.com \
    /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