All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@openembedded.org>
Cc: poky@o-hand.com
Subject: Re: [poky] Syntax for requiring a dependency task's deploy	phase to be finished
Date: Thu, 29 Nov 2007 20:55:47 +0100	[thread overview]
Message-ID: <474F1943.50308@student.utwente.nl> (raw)
In-Reply-To: <1196363431.6917.29.camel@localhost.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Purdie schreef:
> On Thu, 2007-11-29 at 11:53 -0600, Matt Hoosier wrote:
>> I'm trying to build a kernel containing an initramfs linked directly
>> into the kernel binary. This is inspired by the recent discussion
>> here: building a minimal image with IMAGE_FSTYPE set to cpio.
>>
>> I need to be sure that by the time the kernel's do_compile task
>> executes, the minimal image has been deploy to ${DEPLOY_DIR}/image.
>> What's the right way to write this dependency?
> 
> If I understand correctly you want something like
> 
> do_compile[depends] += "minimal-image:do_deploy"
> 
> inside the kernel recipe where "minimal-image" is the name of the image
> recipe.

And make sure *nothing* in that image depends on a kernel at buildtime,
otherwise bitbake will start spewing incomprehensible backtraces :)
A better approach would be to write a bbclass that takes a kernel image
and initramfs and glues those together.

regards,

Koen



- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHTxlDMkyGM64RGpERAhg8AJ9suIHZD8NIXvyK0+FwvVQe1iJoxgCeLMKd
u9K/J91oaRA6WV16kTlpaOs=
=yZ7f
-----END PGP SIGNATURE-----



  reply	other threads:[~2007-11-29 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 17:53 Syntax for requiring a dependency task's deploy phase to be finished Matt Hoosier
2007-11-29 19:10 ` [poky] " Richard Purdie
2007-11-29 19:55   ` Koen Kooi [this message]
2007-11-29 23:44     ` Matt Hoosier

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=474F1943.50308@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=poky@o-hand.com \
    /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.