From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Extending images
Date: Fri, 18 Jul 2014 12:48:33 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407181242001.14141@localhost> (raw)
In-Reply-To: <53C94ACD.6010800@mlbassoc.com>
On Fri, 18 Jul 2014, Gary Thomas wrote:
> I've always used 'IMAGE_INSTALL += " xyz"' in my local.conf
> to add new packages to a build. That said, I had a working
> build for qemuarm (probably doesn't matter) and I added:
> IMAGE_INSTALL += " strace"
> This produced a completely broken image which barely came
> up to a shell, lots of missing programs, etc.
>
> I then tried
> CORE_IMAGE_EXTRA_INSTALL += " strace"
> which produced a perfectly working build (just as previous)
> with the new package added.
>
> I can see that the images produced are vastly different:
>
> * Original working build
> -rw-r--r-- 1 gthomas gthomas 11719 Jul 18 09:34
> core-image-sato-qemuarm-20140718124453.rootfs.manifest
> -rw-r--r-- 1 gthomas gthomas 87611203 Jul 18 09:34
> core-image-sato-qemuarm-20140718124453.rootfs.tar.bz2
>
> * After 'IMAGE_INSTALL += '
> -rw-r--r-- 1 gthomas gthomas 9986 Jul 18 09:55
> core-image-sato-qemuarm-20140718155134.rootfs.manifest
> -rw-r--r-- 1 gthomas gthomas 37859884 Jul 18 09:56
> core-image-sato-qemuarm-20140718155134.rootfs.tar.bz2
>
> * After 'CORE_IMAGE_EXTRA_INSTALL += '
> -rw-r--r-- 1 gthomas gthomas 11738 Jul 18 10:05
> core-image-sato-qemuarm-20140718160108.rootfs.manifest
> -rw-r--r-- 1 gthomas gthomas 87720106 Jul 18 10:05
> core-image-sato-qemuarm-20140718160108.rootfs.tar.bz2
>
> What's the difference and why did the first attempt fail?
i'm going to guess this is related to my recent whining about how
weirdly core-image-* recipes are defined. if i use the "bb" command
to see what will be installed on a qemuarm in a core-image-sato image,
i see:
$ bb show IMAGE_INSTALL -r core-image-sato
Parsing recipes..done.
# IMAGE_INSTALL=${CORE_IMAGE_BASE_INSTALL} packagegroup-core-x11-sato-games
IMAGE_INSTALL="packagegroup-core-boot packagegroup-base-extended \
packagegroup-core-x11-sato-games"
$
which looks good. but the instant i add the line:
IMAGE_INSTALL += "strace" to my local.conf ... whoops:
$ bb show IMAGE_INSTALL -r core-image-sato
Parsing recipes..done.
IMAGE_INSTALL=" strace packagegroup-core-x11-sato-games"
$
note the loss of the essential core-boot and base-extended
packagegroups, which is why your image is broken, which is because of
the way IMAGE_INSTALL is assigned in core-image.bbclass.
lesson: do not mess with IMAGE_INSTALL directly unless you truly
know what you're doing.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-07-18 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 16:26 Extending images Gary Thomas
2014-07-18 16:48 ` Robert P. J. Day [this message]
2014-07-18 16:49 ` Christopher Larson
2014-07-18 16:54 ` Gary Thomas
2014-07-18 17:00 ` Christopher Larson
2014-07-18 18:45 ` Robert P. J. Day
2014-07-18 18:48 ` Christopher Larson
2014-07-18 18:55 ` Robert P. J. Day
2014-07-18 19:07 ` Christopher Larson
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=alpine.LFD.2.11.1407181242001.14141@localhost \
--to=rpjday@crashcourse.ca \
--cc=gary@mlbassoc.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.