[Linaro-dev] linaro build system (was Re: Availability of hardware for Linaro development?)
jay4mail at gmail.com
Sun Jun 6 07:33:56 BST 2010
> > > Would it not make more sense to simply standardize on a readily
> > > available toolchain such as CodeSourcery's Lite ARM toolchain?
> > Excellent suggestion! :-)
> I just subscribed to this maillist and am very interested in build system
> setup for linaro as a long time embedded developer (half of my time on UI
> system and half on BSP/distribution) and of course most on ARM :-)
> I certainly suggest CodeSourcery toolchain too!
> But build system is more than just gcc, binutil and libc and in
> distributions, it is often bound to package system, and tools to create a
> clean chroot to install dependencies automatically.
> Some tools like scratchbox basically "pretend" the cross compiling to be
> native to avoid/minimize special patches for cross compiling (we can't
> guarantee code from upstream are always cross compiling friendly).
> OBS(Opensuse Build System) does native compiling through QEMU and it also
> can be used similar to scratchbox, i.e., native compiling using cross
> gcc, native(x86)bash/perl/python to speed up the build.
> I think Debian/Ubuntu and most other dist are similar to OBS too, while
> traditional embedded linux doesn't have pkg system and using cross
> compiling directly.
> So my question is what will be the default build system, which, I guess,
> is part of deliveries? Since linaro is not a distribution, will it be
> dist-agnostic? (Don't get me wrong as I am a Debian/Ubuntu fan :-) ).
Don't forget about OpenEmbedded: http://www.openembedded.org/
OE can build images for real hardware and for qemu (x86 and qemu-arm).
OE can use external toolchain and can build own (gcc-based).
More information about the Linaro-dev