All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: howto? Build something but not deploy in root image
Date: Mon, 9 Jul 2007 16:42:59 +0200	[thread overview]
Message-ID: <200707091643.00611.openembedded@hrw.one.pl> (raw)
In-Reply-To: <468C7B11.8050809@openhardware.net>

Dnia czwartek, 5 lipca 2007, Tom Walsh napisał:

> I have several parts to this project that must be built during the
> bitbake process (bootstrap-image), but are not part of the target
> filesystem image.  The total system parts are:
>
> * bootloader - ARM - resides in Flash.
> * kernel - ARM - resides in Flash.
> * target rootfs image - ARM - resides on MMC card.
> * Flash Utility - native (x86) - runs on host computer.

In machine config add:

IMAGEDEPENDS = "bootloader flash-utility-native"

Basically it should be MACHINE_EXTRA_DEPENDS but we do not support it yet 
properly.

> The only thing that I need in the root filesystem (tmp/rootfs/) is the
> packages I named from the local conf files. 

Create own image recipe and add those packages to RDEPENDS and 
PACKAGE_INSTALL.

> As to the bootloader, it comes in two sections (files), these are
> programmed by the Flash Utility into the target system.  The bootloader
> is not needed in the root filesystem.

> The problem is not getting these things built, but preventing them from
> being installed in the tmp/rootfs/ filesystem or tarball.  They should
> only go into tmp/deploy/image/, which  I currently have them going
> into...  

Look at uboot/u-boot* recipes and their do_deploy() tasks which copy 
bootloader into tmp/deploy/images/ dir.

> However, the bitbake system assumes that anything that is 
> packaged, must be deployed into the root filesystem!?

No. Image is built from packages, but from selected ones only.

> How do you build a bootloader that resides in Flash and doesn't get
> stuck into the filesystem image?  The same would hold true for the
> native (linux PC) app which flashes the target memory.

In their recipes add do_deploy() task which copies them to 
tmp/deploy/images/ dir.


-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

     Free speech includes the right not to listen, if not interested 
                                                [Robert A. Heinlein]





  parent reply	other threads:[~2007-07-09 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  5:01 howto? Build something but not deploy in root image Tom Walsh
2007-07-05 13:52 ` Justin Patrin
2007-07-05 16:03 ` Paul Sokolovsky
2007-07-09 14:42 ` Marcin Juszkiewicz [this message]
2007-07-15 13:28   ` Tom Walsh
2007-07-15 13:33     ` Koen Kooi
2007-07-15 14:53       ` Holger Freyther

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=200707091643.00611.openembedded@hrw.one.pl \
    --to=openembedded@hrw.one.pl \
    --cc=openembedded-devel@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 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.