All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Peter Tornel <petertornel@yahoo.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: confusion about IMAGE_INSTALL and getting packages into rootfs
Date: Thu, 12 Apr 2012 00:15:47 -0700	[thread overview]
Message-ID: <4F868123.9010902@linux.intel.com> (raw)
In-Reply-To: <1334167325.15462.YahooMailNeo@web122203.mail.ne1.yahoo.com>



On 04/11/2012 11:02 AM, Peter Tornel wrote:
> I'm working with the poky tree, master branch.  I added a few packages
> to IMAGE_INSTALL in core-image-minimal.bb.  Everything builds fine, and
> I can see the built images in each tmp/work subdirectory for my
> IMAGE_INSTALL packages. 
> 
> However, I find that some of the image executables that were part of the
> packages specified in IMAGE_INSTALL wind up in my core-image-minimal
> rootfs and some don't.
> 
> Is there a switch or variable that I need to set to direct all packages
> specified in IMAGE_INSTALL to be installed into my rootfs? 
> 
> 

The preferred way modify the packages that get installed is via the
CORE_IMAGE_EXTRA_INSTALL (POKY_EXTRA_INSTALL in the 1.1 edison release
and earlier) variable in your local.conf. However, modifying the recipe
itself - or writing a new image recipe that sets IMAGE_INSTALL should work.

Can you provide an example of what you have tried that doesn't work?
Keep in mind that you should be using package names here, not recipe names.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-04-12  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 18:02 confusion about IMAGE_INSTALL and getting packages into rootfs Peter Tornel
2012-04-12  7:15 ` Darren Hart [this message]
2012-04-13  0:10   ` Peter Tornel
2012-04-13  0:37     ` Gary Thomas

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=4F868123.9010902@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=petertornel@yahoo.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.