From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Juro Bystricky <juro.bystricky@intel.com>,
openembedded-core@lists.openembedded.org
Cc: jurobystricky@hotmail.com
Subject: Re: [PATCH 1/3] build-appliance-image: use pip3-native
Date: Wed, 15 Mar 2017 22:16:55 +0000 [thread overview]
Message-ID: <1489616215.13980.82.camel@linuxfoundation.org> (raw)
In-Reply-To: <1489616018-8969-2-git-send-email-juro.bystricky@intel.com>
On Wed, 2017-03-15 at 15:13 -0700, Juro Bystricky wrote:
> Do not rely on pip3 being installed on the host.
> Use pip3-native instead.
>
> [YOCTO#10909]
> [YOCTO#11022]
>
> Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
> ---
> meta/recipes-core/images/build-appliance-image_15.0.0.bb | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> index 0db1fb0..730989e 100644
> --- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> +++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
> @@ -18,10 +18,10 @@ IMAGE_ROOTFS_EXTRA_SPACE = "41943040"
> # Do a quiet boot with limited console messages
> APPEND += "rootfstype=ext4 quiet"
>
> -DEPENDS = "zip-native"
> +DEPENDS = "zip-native python3-pip-native"
> IMAGE_FSTYPES = "vmdk"
>
> -inherit core-image module-base
> +inherit core-image module-base setuptools3
>
> SRCREV ?= "8343ed93c4278715aa1582d3cadedf8f197b4089"
> SRC_URI = "git://git.yoctoproject.org/poky;branch=master \
> @@ -95,6 +95,8 @@ fakeroot do_populate_poky_src () {
> echo 'gtk-theme-name = "Clearlooks"' >
> ${IMAGE_ROOTFS}/etc/gtk-2.0/gtkrc
>
> # Install modules needed for toaster
> + export STAGING_LIBDIR=${STAGING_LIBDIR_NATIVE}
> + export STAGING_INCDIR=${STAGING_INCDIR_NATIVE}
> export HOME=${IMAGE_ROOTFS}/home/builder
> mkdir -p ${IMAGE_ROOTFS}/home/builder/.cache/pip
> pip3 install --user -I -U -v -r
> ${IMAGE_ROOTFS}/home/builder/poky/bitbake/toaster-requirements.txt
Looks good, thanks. Can you also drop "pip" from bitbake.conf's
HOSTTOOLS_NONFATAL please?
Cheers,
Richard
next prev parent reply other threads:[~2017-03-15 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 22:13 [PATCH 0/3] Build Appliance tweaks Juro Bystricky
2017-03-15 22:13 ` [PATCH 1/3] build-appliance-image: use pip3-native Juro Bystricky
2017-03-15 22:16 ` Richard Purdie [this message]
2017-03-15 22:57 ` Bystricky, Juro
2017-03-15 22:13 ` [PATCH 2/3] build-appliance-image: fix build errors Juro Bystricky
2017-03-15 22:13 ` [PATCH 3/3] build-appliance-image: ensure pod2man present in BA Juro Bystricky
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=1489616215.13980.82.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=juro.bystricky@intel.com \
--cc=jurobystricky@hotmail.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