public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] basic question
Date: Sun, 09 Apr 2006 07:35:25 -0400	[thread overview]
Message-ID: <1144582525.4566.55.camel@localhost> (raw)
In-Reply-To: <1144459898.28854.11.camel@mrpointy>

On Sat, 2006-04-08 at 11:31 +1000, Geoff O'Callaghan wrote:
> Hi Guys,
> 
> Sorry for such a basic question.   I'm used to openembedded style builds
> which you could say are 'almost' like the gentoo approach to source
> level builds.    I must confess to never having used Gentoo (sorry about
> that ;-)  ) though I like the concept.   And now for the question.
> 
> For a given build (eg cross compile -> ARM flash based system) is the
> Gentoo-embedded methodology to build a flashable image which i'm
> expected to flash OR is there a mechanism for creating something like an
> ipkg that I can install on my existing target - having both options
> gives me a lot of flexibility.  

I'm not aware of any tool in gentoo right now that x-compiles and then 
makes the flash image. Mostly we all merge into an alt ${ROOT} and then 
go run genext2fs/mksqushfs/mkfs.jffs2 or whatever suits your needs for 
the type of flashable image you are creating.
The gnap project does do building, merging and dumps out a flashable
image when it's all done. But afaik gnap is mostly targeted at native
compiles vs x-compiles.

The qmerge util from portage-utils is an ipkg/apt* work alike.

>  So what's the approach for embedded
> gentoo?

Provide the tools & development environment for users and let them 
figure out what's best for the device they own.



-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-embedded@gentoo.org mailing list



      reply	other threads:[~2006-04-09 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08  1:31 [gentoo-embedded] basic question Geoff O'Callaghan
2006-04-09 11:35 ` Ned Ludd [this message]

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=1144582525.4566.55.camel@localhost \
    --to=solar@gentoo.org \
    --cc=gentoo-embedded@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox