Hi Simon, We are using the OpenEmbedded as build system of Mamona. After we have all packages built by OE we add then to a .deb repository and after a debootstrap installation in your pc you will be able to use the Mamona environment with chroot + qemu. This is not an OE stuff but a Mamona approach.
We use the OE to build packages, but we call the Mamona SDK the chroot+qemu environment after the debootstrap install. This SDK is a chroot + qemu, but it differs from scratchbox when it doesn't have targets. it is simplest and more isolated. The use of this sdk is to compile direct for ARM-EABI. Ok, thinking that emulated compilation is slow we have setup a repository called noemu that have packages like gcc and binutils that are i386 binaries that cross-compile making it faster. The idea is to have this emulated environment to developer compile and test their programs and the OpenEmbedded to build the packages. On 9/24/07, Simon Pickering <[EMAIL PROTECTED]> wrote: > > > > > I think that the group developing Mamona are effectively > using a 'native' > > > OpenEmbedded setup within Scratchbox. I don't know how far > > along they are or > > > whether this is a better approach than cross-compiling with > > OpenEmbedded as I'm > > > not really up to speed with OE any more. > > > > Actually, we (from Mamona) are not using the scratchbox neither the > > codesourcery toolchain. We are using the pure OpenEmbedded generated > > toolchain... > > My apologies for the mis-information. You're using qemu & chroot then? I > thought > this is effectively what Scratchbox is? > > In any case you're not using a cross-compiler at the configure & make level, > but > natively compiling due to the use of qemu & chroot? > > Is there any reason for this approach rather than using a cross-compiler, or > has > all OpenEmbedded building gone this way recently? > > Thanks, > > > Simon > > -- Rodrigo Vivi INdT - Instituto Nokia de Tecnologia Blog: http://blog.vivi.eng.br GPG: 0x905BE242 @ wwwkeys.pgp.net _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
