Fwd: GAR for embedded systems

So what your saying is that the GAR tree builds both the target
toolchain (GCC, glibc, etc) and then everything that goes on the
target image.  Is that correct?

For my purposes I want to use a toolchain built with crosstool.  If I
understand correctly, the meta/lnx-bbc directory depends on both the
toolchain build and the target (singularity) build.  So, if I want to
build using my own build environment then I need to make sure that
I've told GAR about my specific build tools and run 'make' in the
meta/singularity directory.  Is this correct?

Thanks,
g.

On Thu, 28 Oct 2004 09:01:00 -0400, jared jennings <[email protected]> wrote:
> On Wed, 27 Oct 2004 15:23:10 -0600, "Grant Likely" <[email protected]>
> said:
> > I noticed that GAR was designed to support
> > cross compiling but I haven't found any examples it being used that
> > way
>
> lnx-bbc cross-compiles both for i386 and powerpc architectures. they
> first began doing this so they could have different versions of
> glibc/gcc and not melt. so when i get the research tree (i think 2.1
> does this too) and go into meta/lnx-bbc and type make, it first
> satisfies build dependencies for things (using the build image) and then
> builds them (using the singularity image). Everything built with
> DESTIMG=singularity on the make command line uses the cross-compiling
> toolset. the make variables that are different are mostly in
> meta/singularity/singularity.conf.mk. e.g. singularity_CC is different
> from build_CC and main_CC. (main is the DESTIMG that gets used for
> whatever you're making if you don't specify one.) there's a different
> subdir under work/ for each image (build.d, singularity.d, main.d).
>
> all the magic for images and cross-compilation is in the meta/ packages
> and gar.mk and gar.conf.mk. well, and there's a little in the kernel/
> Makefiles. but i haven't gotten into kernel/ yet.
>
> hth
> --
>   jared jennings -- [email protected]
>   http://www.fastmail.fm/ it rocks!
>
>