All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf_samuelsson@telia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Building multiple u-boot binaries in oe-core?
Date: Tue, 18 Oct 2011 10:13:59 +0200	[thread overview]
Message-ID: <4E9D3547.4050809@telia.com> (raw)
In-Reply-To: <4E9C975D.60709@telia.com>

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.
Isn't this a good time to get rid of UBOOT_MACHINE altogher
and/or redefine it without the "_config"

P.S: I am working on another project right now, so I don't know
when I have time to test this out on oe-core, so anyone
else interested, feel free to implement it

-- 
Best Regards
Ulf Samuelsson




       reply	other threads:[~2011-10-18  8:19 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 ` Ulf Samuelsson [this message]
2011-10-18  8:25   ` Building multiple u-boot binaries in oe-core? Koen Kooi
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=4E9D3547.4050809@telia.com \
    --to=ulf_samuelsson@telia.com \
    --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.