From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Cc: "openembedded-devel@openembedded.org"
<openembedded-devel@openembedded.org>
Subject: Re: Best way to tune a distro and to build a toolchain for it
Date: Wed, 17 Dec 2008 15:45:25 +0100 [thread overview]
Message-ID: <49491085.1080405@epfl.ch> (raw)
In-Reply-To: <gib2hb$nk2$1@ger.gmane.org>
Thank you for your answer Koen.
Koen Kooi wrote:
> On 17-12-08 15:08, Valentin Longchamp wrote:
>> We have designed a processor board in our laboratory that we are going
>> to use to control our robots for experiments. The board is now supported
>> in OE (mx31moboard machine) and I am very happy to be able to build a
>> Linux distro for our board thank to OE.
>>
>> Until now I have used the Angstrom distro with success. Now since my use
>> is mostly going to be for a robot with no screen (and of course no
>> PIM/agenda, games and these kinds of things) I have always built a
>> console-image. However now I would like to add some packages by default
>> in the images that I want to build for our robot (for instance hal is
>> needed by one of our softs, I would like it to be included by default).
>>
>> I could do this by adding these packages in the MACHINE_EXTRA_RDEPENDS
>> variable in the machine config file, but I think this is more a distro
>> question.
>
> No, it's image question. Stuff that goes into an image is an image
> question. I have multiple devices without a screen and use angstrom on
> it without troubles. There's absolutely no need for yet another distro.
OK. Sorry, there are still some concepts in OE that are a little bit
opaque to me. But I agree, it's definitely an image question. I want an
image that would fit my needs.
>
>> To summarize: what would be the best way to create a "robotic version"
>> of angstrom in OE ?
>
> Create tasks and images for it. There's absolutely no need for yet
> another distro.
>
Of course I don't want to create yet another distro. That's what I meant
by "tuning". But the correct concepts were tasks and an image for for
this task.
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
next prev parent reply other threads:[~2008-12-17 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 14:08 Best way to tune a distro and to build a toolchain for it Valentin Longchamp
2008-12-17 14:32 ` Koen Kooi
2008-12-17 14:45 ` Valentin Longchamp [this message]
2008-12-17 14:41 ` Cliff Brake
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=49491085.1080405@epfl.ch \
--to=valentin.longchamp@epfl.ch \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.