On Wednesday 07 July 2010 14:03:43 Jeremiah Foster wrote:
> On Jul 7, 2010, at 11:31, Jan-Simon Möller wrote:
> > To clarify: these are the basic bits of a x86->ARM cross toolchain for
> > using on a x86 meego host. Building ARM _inside_ OBS works different.
>
> Are there proprietary binaries on the OBS that builds ARM v7?
No! All is there, all is open. Don't mix 'different' with 'proprietary'.
We need more documentation - this is WIP.
> And if yes,
> is it then impossible to duplicate the same build toolchain that exists
> inside the OBS for MeeGo?
If you're on a interlinked OBS, you'll inherit the cross-compiler.
If you're cloning, then you need to do an _exact_ clone.
An high level overview is:
armv5 and armv7 use a cross-compiler build as part of the MeeGo Core and from
the gcc package (currently in Trunk:Testing, gcc+gcc-cross in current Trunk).
This cross-compiler comes in 2 flavours (same applies to binutils):
* cross-armv5tel-gcc.i586.rpm (cross-armv7l-gcc.i586.rpm)
-- this is a cross-compiler running on a MeeGo i586 host compiling for ARM
using /opt/cross as prefix and /opt/cross/<target-tuple>/sysroot as
sysroot. We don't use this in OBS.
* cross-armv5tel-gcc-accel.armv5tel.rpm (cross-armv7l-gcc-accel.armv7l.rpm)
-- this is a cross-compiler designed for OBS internal compilation
it has a specialized prefix, uses changed -rpath. Note the
"armv5tel.rpm/armv7l.rpm" - these claim to be ARM binaries (by
intention), but actually they're i586.
-- this compiler (given all dependencies are installed) will also run in an
chrooted ARM rootfs. This is then very similar to scratchbox, with less
sb-ishms. This is what 'osc build' will download/install to the build
chroot, btw.
HTH.
Best,
Jan-Simon
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
