Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: Steffen Sledz <sledz@dresearch.de>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: u-boot-utils and UBOOT_MACHINE?
Date: Wed, 9 Mar 2011 10:12:03 -0700	[thread overview]
Message-ID: <4D77B4E3.3030305@mentor.com> (raw)
In-Reply-To: <4D7759A1.4060802@dresearch.de>

On 03/09/2011 03:42 AM, Steffen Sledz wrote:
> The current recipe for the u-boot-utils (u-boot-utils_1.2.0.bb) contains this:
>
> ------------------->snip<--------------------
> do_configure() {
>          oe_runmake Sandpoint8240_config
> }
> ------------------->snip<--------------------
>
> This seems to be very machine specific.
>
> I'm not a u-boot-tools specialist. If the tools are not machine specific and the above line is just a placeholder, this should be documented.
>
> But if the tools itself are machine specific i believe there should be something like
>
> ------------------->snip<--------------------
> do_configure() {
>          oe_runmake ${UBOOT_MACHINE}
> }
> ------------------->snip<--------------------
>
> and package build should go into machine specific workdir. Right?

So, currently, and modulo the config files that are shipped per-BSP 
anyhow, the utils that are made are generic.  It's possible, but I 
haven't confirmed, that both this and u-boot-mkimage could just build 
sans a config target, since it's just building in the tools subdir.

-- 
Tom Rini
Mentor Graphics Corporation



      parent reply	other threads:[~2011-03-09 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 10:42 u-boot-utils and UBOOT_MACHINE? Steffen Sledz
2011-03-09 13:12 ` Martyn Welch
2011-03-09 17:12 ` Tom Rini [this message]

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=4D77B4E3.3030305@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=sledz@dresearch.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