public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] frontend needed to make Gentoo/embedded a viability
Date: Sun, 20 Aug 2006 07:30:50 -0400	[thread overview]
Message-ID: <200608200730.51736.vapier@gentoo.org> (raw)
In-Reply-To: <20060812213832.48e03f9a@dukebook.lan>

[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]

On Saturday 12 August 2006 22:38, Yuri Vasilevski wrote:
> Mike Frysinger <vapier@gentoo.org> wrote:
> > so i was tooling along the road thinking about what it would take for
> > people to sit down and use Gentoo/embedded for the target ...
> > currently we have misc ways of doing this by hand (install
> > mask/etc...), but it tends to be error prone and it requires the end
> > user to know more than they should about the portage environment
> >
> > what would help here is a frontend ... something like uClinux or Open
> > Embedded where a menu system allows the user to select the packages
> > to install into the target image and when they're done, they simply
> > type 'make' ... wait a bit and they're left with images that they can
> > take and flash onto the target board
>
> The way I see this, is that this is covered by buildroot, so it would be
> duplicating things at some level to do this with gentoo.

yes, we'd be replacing everything buildroot does that Gentoo doesnt already 
do ... buildroot is really:
 - cross-compiler selection / build
 - package selection / build
 - image generation

now, we already have the first part with crossdev ... the second part we 
mostly have, just need a more user friendly interface

image generation isnt that big of a deal ... that's like running 
`mkfs.<whatever>` on a directory

> > so really, a friendly frontend for the user to select the
> > characteristics of the system, and then a backend to take that config
> > and use emerge to build everything and generate an image ... would
> > make it easy to create stock board descriptions too ...
>
> But I think it would be really nice if we could teach catalyst to
> generate embedded images from some "board" spec files.
> And once this works, a fancy spec file editor with a nice gui could be
> written if needed.

we could take that route of teaching catalyst how to do cross-compiling rather 
than reinventing the wheel
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2006-08-20 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12 23:50 [gentoo-embedded] frontend needed to make Gentoo/embedded a viability Mike Frysinger
2006-08-13  0:13 ` Kevin Winter
2006-08-13  2:11   ` Mike Frysinger
2006-08-13  2:38 ` Yuri Vasilevski
2006-08-20 11:30   ` Mike Frysinger [this message]
2006-08-13  8:43 ` Ned Ludd
2006-08-13 10:49   ` Thierry Carrez
2006-08-14  0:50 ` wireless

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=200608200730.51736.vapier@gentoo.org \
    --to=vapier@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