From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 1/2] give nice output when generating barebox.bin and barebox.S
Date: Fri, 22 Jan 2010 16:14:34 +0100 [thread overview]
Message-ID: <1264173275-1858-1-git-send-email-u.kleine-koenig@pengutronix.de> (raw)
In-Reply-To: <20100122150628.GA12856@pengutronix.de>
As a side effect don't build barebox.S when barebox.bin is updated. I
didn't manage to keep the old behaviour and I consider it cleaner this
way.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
Makefile | 15 ++++++++++++---
1 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/Makefile b/Makefile
index 0c00829..5b5c2e8 100644
--- a/Makefile
+++ b/Makefile
@@ -641,9 +641,18 @@ define rule_barebox-modpost
$(Q)echo 'cmd_$@ := $(cmd_barebox-modpost)' > $(dot-target).cmd
endef
-barebox.bin: barebox
- $(Q)$(OBJCOPY) -O binary barebox barebox.bin
- $(Q)$(OBJDUMP) -d barebox > barebox.S
+quiet_cmd_objcopy = OBJCOPY $@
+ cmd_objcopy = $(OBJCOPY) $(OBJCOPYFLAGS) $(OBJCOPYFLAGS_$(@F)) $< $@
+
+OBJCOPYFLAGS_barebox.bin = -O binary
+barebox.bin: barebox FORCE
+ $(call if_changed,objcopy)
+#$(Q)$(OBJCOPY) -O binary barebox barebox.bin
+
+quiet_cmd_disasm = DISASM $@
+ cmd_disasm = $(OBJDUMP) -d $< > $@
+barebox.S: barebox FORCE
+ $(call if_changed,disasm)
# barebox image
barebox: $(barebox-lds) $(barebox-head) $(barebox-common) $(kallsyms.o) FORCE
--
1.6.6
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-01-22 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 15:06 [PATCH] arm cache fixes Uwe Kleine-König
2010-01-22 15:14 ` Uwe Kleine-König [this message]
2010-03-12 9:51 ` [PATCH] give nice output when generating barebox.bin and barebox.S Uwe Kleine-König
2010-01-22 15:14 ` [PATCH 2/2] arm: make disabling the cache actually work Uwe Kleine-König
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=1264173275-1858-1-git-send-email-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox