[Linaro-dev] linaro build system (was Re: Availability of hardware for Linaro development?)

Shaz shazalive at gmail.com
Sun Jun 6 07:03:40 BST 2010


On Sun, Jun 6, 2010 at 10:37 AM, Mark Mitchell <mark at codesourcery.com> wrote:
> JD Zheng wrote:
>
>> 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.
>
> Yes, that's correct -- and that is indeed one of the challenges of
> cross-compilation for Linux targets.  The configuration of the compiler
> determines to some extent where it expects shared libraries to be
> located at run-time, and where it expects headers to be found (relative
> to the sysroot) at compile-time.  Sometimes, this means that you have to
> use command-line options to help the poor compiler cope with a Linux
> distribution that doesn't have things where the compiler expects them to be.
>
>> 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 :-) ).
>
> Just so that nobody things I'm ignoring this question, I'll answer it: I
> have no idea.  I didn't promise a useful answer! Seriously, this just
> isn't something I know anything about; I'm sure that the Linaro folks
> have a much better answer.

Keep openembedded and bitbake in mind because it is very flexible.



-- 
Shaz



More information about the Linaro-dev mailing list