From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mike Frysinger <vapier@gentoo.org>
Date: Mon, 17 Nov 2008 17:46:09 -0500
Subject: [U-Boot] Building tools without building firmware
In-Reply-To: <4921F2A3.3010200@genesi-usa.com>
References: <4919E7CD.2060005@genesi-usa.com>
	<200811171641.05060.vapier@gentoo.org>
	<4921F2A3.3010200@genesi-usa.com>
Message-ID: <200811171746.09728.vapier@gentoo.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Monday 17 November 2008 17:39:31 Matt Sealey wrote:
> Mike Frysinger wrote:
> > On Monday 17 November 2008 16:05:44 Matt Sealey wrote:
> >> Mike Frysinger wrote:
> >>> On Tuesday 11 November 2008 15:15:09 Matt Sealey wrote:
> >>>> We have a need to build and package at the very least 'mkimage' for
> >>>> SuSE 11.1 and since we have multiple board targets in mind (MPC8641D,
> >>>> MPC8610, MPC5121e) it does not make any sense to pick any in
> >>>> particular or build the entire u-boot.bin just for a few kilobytes we
> >>>> need to prep kernels and initrd images.
> >>>>
> >>>> Is it possible to simply build the tools/ directory (a make target
> >>>> that works would be great) without building a firmware from
> >>>> BLAH_config first?
> >>>
> >>> you can see the method we use in Gentoo here:
> >>> http://sources.gentoo.org/dev-embedded/u-boot-tools/
> >>
> >> Ouch.
> >>
> >>> but i'd agree that i wish it were easier to just build the helper
> >>> utilities. and if they werent so tightly intertwined with the rest of
> >>> the u-boot code ... atm you cant build mkimage on a non-Linux system
> >>> due to the libfdt stuff.
> >>
> >> Am I reading this right.. I'm using SUSE 11.0 here so I guess I do
> >>
> >> touch include/config.h include/config.mk
> >> make HOSTSTRIP=echo BIN_FILES="mkimage"
> >>
> >> And that'd do it? I'll have to check it out later..
> >
> > should be ... seemed to work for me
> >
> > btw, we do HOSTSTRIP=echo in Gentoo only because we dont let packages
> > strip things themselves ... it's not like u-boot will break things
> > otherwise
>
> It doesn't work; I get a lot of errors about asm/blah.h include files being
> missing.
>
> make MPC8610HPCN_config
> make BIN_FILES="mkimage"
>
> this works fine though. I also tried filling out ARCH=ppc into config.mk
> just in case, but it's obvious some weird arch setup is being done to glue
> in the right includes. So, I symlinked asm-ppc to asm, just like mkconfig
> does, and this made it at least get to compile.
>
> So the correct solution is;
>
> touch include/config.h include/config.mk
> ln -sf include/asm-ppc include/asm
> make BIN_FILES="mkimage" tools
>
> (this also builds bmp_logo for some reason.. I don't quite understand why?)

while yes, you'll see a lot of errors, they dont actually matter.  just ignore 
them and you'll get the right tools built up.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20081117/0364ae55/attachment.pgp