From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: saul.wold@intel.com
Subject: [PATCH] timage_types_wic: reschedule do_prepare_wic_build
Date: Thu, 25 May 2017 15:44:55 +0300 [thread overview]
Message-ID: <1495716295-14065-1-git-send-email-ed.bartosh@linux.intel.com> (raw)
In-Reply-To: <1495492710.16848.2.camel@intel.com>
do_prepare_wic_build depended on do_deploy task of EFI_PROVIDER recipe.
This approach didn't work on meta-intel as there is no EFI_PROVIDER
recipe in that layer.
Scheduled do_prepare_wic_build after do_bootimg to fix the issue.
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
---
meta/classes/image_types_wic.bbclass | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/meta/classes/image_types_wic.bbclass b/meta/classes/image_types_wic.bbclass
index 3b73261..baf375b 100644
--- a/meta/classes/image_types_wic.bbclass
+++ b/meta/classes/image_types_wic.bbclass
@@ -70,10 +70,11 @@ python () {
# 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')))
+ bb.build.addtask('do_prepare_wic_build', 'do_image_wic', 'do_bootimg', d)
+ d.appendVarFlag('do_prepare_wic_build', 'depends', 'virtual/kernel:do_deploy')
+ else:
+ bb.build.addtask('do_prepare_wic_build', 'do_image_wic', None, d)
}
#
--
2.1.4
next parent reply other threads:[~2017-05-25 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1495492710.16848.2.camel@intel.com>
2017-05-25 12:44 ` Ed Bartosh [this message]
2017-05-25 13:01 ` ✗ patchtest: failure for timage_types_wic: reschedule do_prepare_wic_build Patchwork
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=1495716295-14065-1-git-send-email-ed.bartosh@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