public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC:  "make DESTDIR=xxx install" ?
Date: Thu, 13 Aug 2009 22:29:40 +0200	[thread overview]
Message-ID: <4A8477B4.2000007@atmel.com> (raw)
In-Reply-To: <Pine.LNX.4.64ksi.0908131104080.988@home-gw.koi8.net>

ksi at koi8.net skrev:
> On Thu, 13 Aug 2009, Ulf Samuelsson 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".
>>
>> Since you may want to put the binaries for several
>> boards in the same directory (like /tftpboot)
>> it is not always good to call the binary simply u-boot.bin.
>>
>> I guess "make DESTDIR=<destination> TARGET=<name> install" would work
>>
>> Alternatively, we collect the final binary from several variables,
>>
>> openembedded typically calls the end binary:
>> ${MACHINE}-u-boot-${U_BOOT_VERSION}-${REVISION}.bin
>>
>> Feedback?
> 
> IMHO it is not worth the effort... U-Boot builds its binary in source root
> and there is no "make install" at all. When one builds RPM or whatever
> packages (as I do) it is not big deal to move the resulting binary elsewhere
> with a single "mv" command.
> 

You forget that things change, and the "make install" puts
the responsibility for handling the installation inside u-boot
instead of outside u-boot.


u-boot is not only u-boot, since you have u-boot-tools
which are used to create the image and also
tools which can be running on the target.

Assume that a tool for the target is added
and other tools rely on that tool?
Since you have not updated your external Makefile
to also "mv" that file, you will be delivering
a broken system.

The effort is probably considerably less than what is spent
on discussing many items on this list.


> ---
> ******************************************************************
> *  KSI at home    KOI8 Net  < >  The impossible we do immediately.  *
> *  Las Vegas   NV, USA   < >  Miracles require 24-hour notice.   *
> ******************************************************************
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot

      reply	other threads:[~2009-08-13 20:29 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
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 [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=4A8477B4.2000007@atmel.com \
    --to=ulf.samuelsson@atmel.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