public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Cam <camilo@mesias.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] tiny patch for examples/Makefile (objcopy related)
Date: Wed, 10 Dec 2003 21:17:09 +0000	[thread overview]
Message-ID: <3FD78D55.6050700@mesias.co.uk> (raw)
In-Reply-To: <20031210163438.GA6906@mvista.com>

George

I have a preference for generating the srec and binary outputs from a 
common input, it seems simpler, and less prone to things going wrong. I 
realise that the current Makefile achieves this in an obscure way (the 
bin is made dependent on the srec, however it really depends on a file 
produced as a side-effect of the srec target).

> This works without the side-effects too:   ; P
[...]
> +	$(OBJCOPY) -I srec -O binary $< $@ 2>/dev/null

I really like that, because it is simple. However it does not work for 
me, as the MontaVista ppc_82xx-objcopy does not support srec input.

If I get some time I will try to do more with the Makefiles, as I would 
like them to work for Rational ClearCase make (clearmake). Mostly they 
do right now with the exception of recursive make invocations. However 
there are greater priorities within the project and I expect I might not 
get the time to tweak the Makefiles beyond getting it working.

Thanks for the feedback, it's a joy to find such an active and 
interested community.

-Cam

      reply	other threads:[~2003-12-10 21:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 13:50 [U-Boot-Users] tiny patch for examples/Makefile (objcopy related) Cam
2003-12-03 15:32 ` George G. Davis
2003-12-07 20:05 ` Wolfgang Denk
2003-12-10 16:13   ` Detlev Zundel
2003-12-10 16:37     ` George G. Davis
2003-12-10 21:17       ` Cam [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=3FD78D55.6050700@mesias.co.uk \
    --to=camilo@mesias.co.uk \
    --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