From: "Eren Türkay" <eren@hambedded.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: IMAGE_INSTALL_append workflow
Date: Mon, 26 Nov 2012 21:04:07 +0200 [thread overview]
Message-ID: <20121126190407.GA69689@gmail.com> (raw)
In-Reply-To: <CAHUNapSVRuxDxn9L=oHg6aO-RKso2VNF6Mczaf2zwgxHn2zzBw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]
On Mon, Nov 26, 2012 at 10:47:31AM -0500, Trevor Woerner wrote:
> I'm kinda surprised nobody jumped in on this one; either my question
> is so silly it isn't worth anyone's time, or I'm the only one who
> wants to add packages to an image after a full build. I know my
> question has nothing to do with trace-cmd specifically, adding any
> package after a full build results in the same problem.
I don't think you are the first person who wants to add a package to image after
the image has been built :)
The obvious problem would have been leading spaces in IMAGE_INSTALL_append but
you explicitly stated its correct. Normally, the class that's responsible for
image creation (image.bbclass) depends on the packages defined in IMAGE_INSTALL
so that the packages are built before the image creation begins.
image.bbclass, line 9
---------------------
RDEPENDS += "${IMAGE_INSTALL} ${LINGUAS_INSTALL} ${NORMAL_FEATURE_INSTALL}
${ROOTFS_BOOTSTRAP_INSTALL}"
On irc (#oe), Eric Benard tried IMAGE_INSTALL_append = " trace-cmd" after a full
build and reported that it built fine. I'm CCing him.
I believe that it will be better to include your <image> file and the files that
you changed so that it will be easier to debug. Mentioning your layers,
configuration, version of Yocto you use will also be helpful.
Regards,
Eren
--
. 73! DE TA1AET
http://erenturkay.com/
[-- Attachment #2: Type: application/pgp-signature, Size: 850 bytes --]
next prev parent reply other threads:[~2012-11-26 19:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 18:27 IMAGE_INSTALL_append workflow Trevor Woerner
2012-11-26 15:47 ` Trevor Woerner
2012-11-26 19:04 ` Eren Türkay [this message]
2012-11-26 21:25 ` Aws Ismail
2012-11-26 22:53 ` Robert P. J. Day
2012-11-26 23:52 ` Trevor Woerner
2012-11-27 2:20 ` Trevor Woerner
2012-11-27 10:39 ` Eric Bénard
2012-11-27 13:40 ` Trevor Woerner
2012-11-27 16:11 ` Eren Türkay
2012-11-27 17:24 ` Robert P. J. Day
2012-11-27 17:42 ` Trevor Woerner
2012-11-27 17:52 ` Robert P. J. Day
2012-11-27 20:11 ` Robert P. J. Day
2012-11-28 4:48 ` Trevor Woerner
2012-11-27 17:44 ` Eric Bénard
2012-11-27 14:00 ` Jonas Jonsson L
2012-11-27 14:04 ` Eric Bénard
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=20121126190407.GA69689@gmail.com \
--to=eren@hambedded.org \
--cc=twoerner@gmail.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.