* Best way to tune a distro and to build a toolchain for it
@ 2008-12-17 14:08 Valentin Longchamp
2008-12-17 14:32 ` Koen Kooi
2008-12-17 14:41 ` Cliff Brake
0 siblings, 2 replies; 4+ messages in thread
From: Valentin Longchamp @ 2008-12-17 14:08 UTC (permalink / raw)
To: openembedded-devel@lists.openembedded.org
Hello,
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.
To summarize: what would be the best way to create a "robotic version"
of angstrom in OE ?
The second question is about toolchains. This platform is going to be
used by many other labs that are going to use our robots or at least our
hardware. I would like to be able to build a "sdk" for them, with all
the libs that we include by default in their sdk (because I already fear
all the mechanical engineers that would have to build OE ...). I can
build meta-toolchain, but how could I tune a toolchain so that it
includes for instance all the headers for the libs that I would add in
my "robotic version" of anstrom ?
Thank you for your help.
Val
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Best way to tune a distro and to build a toolchain for it
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
2008-12-17 14:41 ` Cliff Brake
1 sibling, 1 reply; 4+ messages in thread
From: Koen Kooi @ 2008-12-17 14:32 UTC (permalink / raw)
To: openembedded-devel
On 17-12-08 15:08, Valentin Longchamp wrote:
> Hello,
>
> 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.
> 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.
> The second question is about toolchains. This platform is going to be
> used by many other labs that are going to use our robots or at least our
> hardware. I would like to be able to build a "sdk" for them, with all
> the libs that we include by default in their sdk (because I already fear
> all the mechanical engineers that would have to build OE ...). I can
> build meta-toolchain, but how could I tune a toolchain so that it
> includes for instance all the headers for the libs that I would add in
> my "robotic version" of anstrom ?
Have a look at meta-sdk*.bb, that shows how you can install packages
into a toolchain.
regards,
Koen
>
> Thank you for your help.
>
> Val
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Best way to tune a distro and to build a toolchain for it
2008-12-17 14:32 ` Koen Kooi
@ 2008-12-17 14:45 ` Valentin Longchamp
0 siblings, 0 replies; 4+ messages in thread
From: Valentin Longchamp @ 2008-12-17 14:45 UTC (permalink / raw)
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Best way to tune a distro and to build a toolchain for it
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:41 ` Cliff Brake
1 sibling, 0 replies; 4+ messages in thread
From: Cliff Brake @ 2008-12-17 14:41 UTC (permalink / raw)
To: openembedded-devel
On Wed, Dec 17, 2008 at 9:08 AM, Valentin Longchamp
<valentin.longchamp@epfl.ch> wrote:
> Hello,
>
> 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.
>
> To summarize: what would be the best way to create a "robotic version" of
> angstrom in OE ?
Define a custom image: http://bec-systems.com/web/content/view/79/9/
Cliff
--
=======================
Cliff Brake
http://bec-systems.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-12-17 14:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2008-12-17 14:41 ` Cliff Brake
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.