Re: GAR for embedded systems

Great!  GAR seems to be exactly what I need.  In fact, my embedded
platform should turn out to be simpler than the LNX-BBC because I
don't need both an initrd and a secondary image mounted by it.

I'm having some difficulty understanding just how the LNX-BBC build is
set up.  I've been looking through the documentation but I have not
been able to get an understanding of what the dependancies are between
each of stages (build, main, singularity) and what is contained in
each of them.

I believe that the singularity is the basic image.  If I go into the
meta/singularity directory can I configure it to build just a rootfs
image using my own toolchain?  I'd like to stick with my crosstool
generated toolchain.  I think what I need to do is create my own
target directory under meta/ for my embedded target and then depend on
each of the packages that I want installed.  Is this correct?

Also, how to I specify which target (i386 or PPC) when building the LNX-BBC?

Thanks,
g. 

On Fri, 29 Oct 2004 21:20:33 -0400, Nate Riffe <[email protected]> wrote:
> I cannot believe Grant Likely said this on the ENTARNET:
> > Is anybody actively using GAR to build the rootfs for embedded linux
> > systems?
> 
> No one that I know of, but it's an application for GAR that's been in
> the back of my mind for a long time.  In some ways, though, the
> LNX-BBC is a lot like an embedded system.
> 
> > I'm currently building my rootfs by hand for an Arm/Xscale system.
> > I'm building it by hand at the moment, but GAR looks to be a good fit
> > for automating the build.  I noticed that GAR was designed to support
> > cross compiling but I haven't found any examples it being used that
> > way
> 
> The LNX-BBC build uses it that way.  The cross-compiler it builds
> targets the same architecture as the build system, but not the same
> platform.  The idea is to isolate the binaries on the LNX-BBC as much
> as possible from the binaries on the build system, and a
> cross-compiler provides that separation.  One of the problems that we
> consistently run into is that although we're building a complete
> cross-dev environment, some of the packages we build for the LNX-BBC
> don't support cross-compiling, and end up configured against the build
> system's arch and libraries in spite of our efforts.  That's really
> the only thing holding the LNX-BBC back from true build platform
> independence at this point.
> 
> -Nate
> 
> --
> --< ((\))< >----< [email protected] >----< http://www.movealong.org/ >--
> pub  1024D/05A058E0 2002-03-07 Nate Riffe (06-Mar-2002) <[email protected]>
>      Key fingerprint = 0DAC F5CB D182 3165 D757  C466 CD42 12A8 05A0 58E0
> 
> _______________________________________________
> Lnx-bbc-devel mailing list
> [email protected]
> http://zork.net/mailman/listinfo/lnx-bbc-devel
>