From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building multiple u-boot binaries in oe-core?
Date: Tue, 18 Oct 2011 10:25:08 +0200 [thread overview]
Message-ID: <j7jd54$gnc$1@dough.gmane.org> (raw)
In-Reply-To: <4E9D3547.4050809@telia.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 18-10-11 10:13, Ulf Samuelsson schreef:
> I added the functionality for building multiple u-boot binaries to
> classic openembedded, but this has not been implemented in oe-core. I
> find that rather useful. Anyone disagreeing?
>
> The core of this is:
>
> do_compile () { if ! [ "x${UBOOT_MACHINES}" == "x" ] ; then for board in
> ${UBOOT_MACHINES} ; do if ! [ `grep ${board}_config Makefile | wc -c` ==
> 0 ] ; then mkdir -p binaries/${board} oe_runmake O=binaries/${board}
> distclean oe_runmake O=binaries/${board} ${board}_config oe_runmake
> O=binaries/${board} all fi done else oe_runmake ${UBOOT_MACHINE}
> oe_runmake all fi }
>
> Note that I removed the _config part from UBOOT_MACHINES.
>
> At the moment, the binary after youv'e done "make beagleboard_config;
> make" will be called: u-boot-beagleboard_config-${PV}-${PR}.bin
>
> I think "u-boot-beagleboard-${PV}-${PR}.bin" is nicer.
>
> There aren't that many boards in oe-core at the moment.
4 qemu machine to be exact
> Isn't this a good time to get rid of UBOOT_MACHINE altogher and/or
> redefine it without the "_config"
Not sure, there are a *lot* of BSPs out there where _config is expected to
be there.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFOnTfkMkyGM64RGpERAhgKAJ934JngAAMd33iLVGrYVKYKJ7Am8ACfaxKL
GdSJOI5qgK2eFk7OwHwD3eU=
=62Sb
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-10-18 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E9C975D.60709@telia.com>
2011-10-18 8:13 ` Building multiple u-boot binaries in oe-core? Ulf Samuelsson
2011-10-18 8:25 ` Koen Kooi [this message]
2011-10-18 11:56 ` Ulf Samuelsson
2011-10-18 21:01 ` McClintock Matthew-B29882
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='j7jd54$gnc$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.