Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: rebecca.swee.fun.chang@intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2 0/5] Enable wic in eSDK
Date: Fri, 12 Jan 2018 11:20:59 +0200	[thread overview]
Message-ID: <20180112092059.3sja5c337jinx4nv@linux.intel.com> (raw)
In-Reply-To: <cover.1515681706.git.rebecca.swee.fun.chang@intel.com>

On Thu, Jan 11, 2018 at 10:55:18PM +0800, rebecca.swee.fun.chang@intel.com wrote:
> Hi all,
> 
> As the subject called out: this patch series enable wic in eSDK.
> The details of what I have done are documented within the commit message.
> Basically wic requires an OE build environment, but we are using a
> different environment setup script in eSDK. Hence, I have added some
> code for wic to explicitly export bitbake variables within eSDK. I
> have also make wic to use the shared code in scriptpath for oe lib
> and bitbake path addition to sys.path.
> 
> I have run the changes on wic oe-selftest and the tests are passing.
> What's next: I think it would better to have some test cases
> for wic within eSDK if this series are merged.
> 

Would it make sense to cover this new functionality by tests?

> 
> The following changes since commit 364f8bcfcbd04e722490f363ad36a15fb7066ba7:
> 
>   linux-firmware: Bump revision to 65b1c68c (2018-01-11 10:26:07 +0000)
> 
> are available in the Git repository at:
> 
>   git://push.yoctoproject.org/poky-contrib rebeccas/wic-dev
> 
> Chang Rebecca Swee Fun (5):
>   scripts/wic: use scriptpath module to find bitbake path and oe lib
>     path
>   scripts/wic: append bitbake executable file path in eSDK environment
>   scripts/wic: fix error of import wic module in eSDK environment
>   scripts/wic: explicitly set BUILDDIR within eSDK
>   classes/populate_sdk_ext: support wic in eSDK
> 
>  meta/classes/populate_sdk_ext.bbclass |  2 +-
>  scripts/wic                           | 23 ++++++++++++++++++-----
>  2 files changed, 19 insertions(+), 6 deletions(-)
> 
> -- 
> 2.15.0
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
--
Regards,
Ed


  parent reply	other threads:[~2018-01-12 11:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 14:55 [PATCHv2 0/5] Enable wic in eSDK rebecca.swee.fun.chang
2018-01-11 14:55 ` [PATCHv2 1/5] scripts/wic: use scriptpath module to find bitbake path and oe lib path rebecca.swee.fun.chang
2018-01-11 14:55 ` [PATCHv2 2/5] scripts/wic: append bitbake executable file path in eSDK environment rebecca.swee.fun.chang
2018-01-11 14:55 ` [PATCHv2 3/5] scripts/wic: fix error of import wic module " rebecca.swee.fun.chang
2018-01-11 14:55 ` [PATCHv2 4/5] scripts/wic: explicitly set BUILDDIR within eSDK rebecca.swee.fun.chang
2018-01-11 14:55 ` [PATCHv2 5/5] classes/populate_sdk_ext: support wic in eSDK rebecca.swee.fun.chang
2018-01-12  9:20 ` Ed Bartosh [this message]
2018-01-15  0:48   ` [PATCHv2 0/5] Enable " Chang, Rebecca Swee Fun

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=20180112092059.3sja5c337jinx4nv@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rebecca.swee.fun.chang@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