From: rebecca.swee.fun.chang@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv2 0/5] Enable wic in eSDK
Date: Thu, 11 Jan 2018 22:55:18 +0800 [thread overview]
Message-ID: <cover.1515681706.git.rebecca.swee.fun.chang@intel.com> (raw)
From: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>
Hi all,
Resend as v2 as I realized an issue with BUILDDIR being set
was not correct. I made the correction on Patch 4 by setting
BUILDDIR to sdkroot variable (eSDK base path) before we alter
the variable for bitbake executable file path.
Regards,
Rebecca
-----
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.
Thanks.
Regards,
Rebecca
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
next reply other threads:[~2018-01-11 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 14:55 rebecca.swee.fun.chang [this message]
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 ` [PATCHv2 0/5] Enable " Ed Bartosh
2018-01-15 0:48 ` 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=cover.1515681706.git.rebecca.swee.fun.chang@intel.com \
--to=rebecca.swee.fun.chang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox