1 |
On Sat, 2006-04-08 at 11:31 +1000, Geoff O'Callaghan wrote: |
2 |
> Hi Guys, |
3 |
> |
4 |
> Sorry for such a basic question. I'm used to openembedded style builds |
5 |
> which you could say are 'almost' like the gentoo approach to source |
6 |
> level builds. I must confess to never having used Gentoo (sorry about |
7 |
> that ;-) ) though I like the concept. And now for the question. |
8 |
> |
9 |
> For a given build (eg cross compile -> ARM flash based system) is the |
10 |
> Gentoo-embedded methodology to build a flashable image which i'm |
11 |
> expected to flash OR is there a mechanism for creating something like an |
12 |
> ipkg that I can install on my existing target - having both options |
13 |
> gives me a lot of flexibility. |
14 |
|
15 |
I'm not aware of any tool in gentoo right now that x-compiles and then |
16 |
makes the flash image. Mostly we all merge into an alt ${ROOT} and then |
17 |
go run genext2fs/mksqushfs/mkfs.jffs2 or whatever suits your needs for |
18 |
the type of flashable image you are creating. |
19 |
The gnap project does do building, merging and dumps out a flashable |
20 |
image when it's all done. But afaik gnap is mostly targeted at native |
21 |
compiles vs x-compiles. |
22 |
|
23 |
The qmerge util from portage-utils is an ipkg/apt* work alike. |
24 |
|
25 |
> So what's the approach for embedded |
26 |
> gentoo? |
27 |
|
28 |
Provide the tools & development environment for users and let them |
29 |
figure out what's best for the device they own. |
30 |
|
31 |
|
32 |
|
33 |
-- |
34 |
Ned Ludd <solar@g.o> |
35 |
Gentoo Linux |
36 |
|
37 |
-- |
38 |
gentoo-embedded@g.o mailing list |