From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "Ahsan, Noor" <Noor_Ahsan@mentor.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Khandavilli, Arun" <Arun_Khandavalli@mentor.com>,
"Larson, Chris" <Chris_Larson@mentor.com>
Subject: Re: Using wic from a Bitbake task
Date: Tue, 28 Jul 2015 14:09:46 +0300 [thread overview]
Message-ID: <20150728110946.GB2320@linux.intel.com> (raw)
In-Reply-To: <365E1805BC95084CBE82381A0B86999401095B33DF@EU-MBX-01.mgc.mentorg.com>
On Mon, Jul 27, 2015 at 12:49:12PM +0000, Ahsan, Noor wrote:
> May I know it’s expected completion date?
I hope to get it done till the end of August. This bug has the highest
priority, so I'll start working on it as soon as I'm back to wic
development.
> Noor
>
> From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Burton, Ross
> Sent: Monday, July 27, 2015 3:05 PM
> To: Usman, Fahad
> Cc: yocto@yoctoproject.org; Khandavilli, Arun
> Subject: Re: [yocto] Using wic from a Bitbake task
>
>
> On 26 July 2015 at 18:24, Usman, Fahad <Fahad_Usman@mentor.com<mailto:Fahad_Usman@mentor.com>> wrote:
> Is it possible to invoke 'wic create' command from a bitbake task. As currently it is implemented to be run as a standalone tool and if we invoke it from a task, the 'bitbake -e' command fails, since more than one instances of bitbake cannot be run from a single build directory.
>
> Not yet, but there's a bug for that:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7672
>
> Ross
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
--
Regards,
Ed
prev parent reply other threads:[~2015-07-28 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 17:24 Using wic from a Bitbake task Usman, Fahad
2015-07-27 7:17 ` Ahsan, Noor
2015-07-27 10:04 ` Burton, Ross
2015-07-27 12:49 ` Ahsan, Noor
2015-07-27 13:01 ` Burton, Ross
2015-07-28 11:09 ` Ed Bartosh [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=20150728110946.GB2320@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=Arun_Khandavalli@mentor.com \
--cc=Chris_Larson@mentor.com \
--cc=Noor_Ahsan@mentor.com \
--cc=yocto@yoctoproject.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.