From: Matt Sealey <matt@genesi-usa.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building tools without building firmware
Date: Mon, 17 Nov 2008 16:39:31 -0600 [thread overview]
Message-ID: <4921F2A3.3010200@genesi-usa.com> (raw)
In-Reply-To: <200811171641.05060.vapier@gentoo.org>
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?)
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
next prev parent reply other threads:[~2008-11-17 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:15 [U-Boot] Building tools without building firmware Matt Sealey
2008-11-16 17:30 ` Mike Frysinger
2008-11-17 21:05 ` Matt Sealey
2008-11-17 21:41 ` Mike Frysinger
2008-11-17 22:39 ` Matt Sealey [this message]
2008-11-17 22:46 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4921F2A3.3010200@genesi-usa.com \
--to=matt@genesi-usa.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox