public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC: "make DESTDIR=xxx install" ?
Date: Thu, 13 Aug 2009 20:06:53 +0200	[thread overview]
Message-ID: <20090813180653.CFB3F833DBD2@gemini.denx.de> (raw)
In-Reply-To: <4A843392.4020800@atmel.com>

Dear Ulf Samuelsson,

In message <4A843392.4020800@atmel.com> you wrote:
> Many packages support installing the resulting binary in another
> location, but U-Boot does not.
> 
> When you use buildsystems like buildroot and openembedded,
> you want to collect the end result in a target directory,
> and while you can use internal knowledge about u-boot
> to do so, it seems cleaner to me, to do a "make DESTDIR install".

Did you consider using out-of-tree builds for that? 

> Since you may want to put the binaries for several
> boards in the same directory (like /tftpboot)

In my experience this is not exactly a lucky choice; if youu have to
maintain more than just a few boards, you definitely want to have a
subdirectory per board in /tftpboot.

> it is not always good to call the binary simply u-boot.bin.

...which then is not problem any more.

> I guess "make DESTDIR=<destination> TARGET=<name> install" would work
> 
> Alternatively, we collect the final binary from several variables,

One question remains: what is "the final binary"?  for  example,  for
the  "kilauea"  board  it  may be "u-boot.bin" (when booting from NOR
flash), but it might also be "u-boot-nand.bin" (when booting from NOR
flash). Oh, and board "foo"  uses  not  the  binary  image,  but  the
S-Record  file  in  their factory installer, so we use "u-boot.srec".
Another  board  requires  am  Intel  hex   image,   so   they   build
"u-boot.hex". For the Marvell processors, we will use a special image
format,  so  it's "u-boot.kwb". BlackFin uses some similar mechanism,
but a different name, IIRC.

And no, we definitlely do not always want to build (and install) all
these images. That would be just a waste of resources.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
I can't say I've ever been lost, but I was bewildered once for  three
days.                                     - Daniel Boone (Attributed)

  reply	other threads:[~2009-08-13 18:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 15:38 [U-Boot] RFC: "make DESTDIR=xxx install" ? Ulf Samuelsson
2009-08-13 18:06 ` Wolfgang Denk [this message]
2009-08-13 20:29   ` Ulf Samuelsson
2009-08-13 21:03     ` Wolfgang Denk
2009-08-15  5:01       ` Ulf Samuelsson
2009-08-15  6:32         ` Wolfgang Denk
2009-08-15  9:35           ` Ulf Samuelsson
2009-08-15 10:42             ` Wolfgang Denk
2009-08-13 18:06 ` ksi at koi8.net
2009-08-13 20:29   ` Ulf Samuelsson

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=20090813180653.CFB3F833DBD2@gemini.denx.de \
    --to=wd@denx.de \
    --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