From: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com>
To: buildroot@busybox.net
Subject: [Buildroot] make source-check
Date: Sun, 15 Jul 2007 14:41:03 +0200 (CEST) [thread overview]
Message-ID: <0707151431170.6891@somehost> (raw)
In-Reply-To: <20070709102348.GA21001@aon.at>
On Mon, 9 Jul 2007, Bernhard Fischer wrote:
> On Mon, Jul 09, 2007 at 12:01:08PM +0200, Cristian Ionescu-Idbohrn wrote:
> >On Mon, 9 Jul 2007, Bernhard Fischer wrote:
>
> >But, wouldn't you agree that doing the same thing witout changing the
> >.config could be a much more elegant way to do it?
>
> If you have a better impl than my quick-hack, i'm eager to see it, sure.
Looks like there might be another way: see info-node "6.10 Target-specific
Variable Values" in a recent manual. What do you think of something like:
--- Makefile (revision 19052)
+++ Makefile (working copy)
@@ -222,11 +222,8 @@
source: $(TARGETS_SOURCE) $(HOST_SOURCE)
-.config.check: dependencies
- $(SED) '/BR2_WGET/s/\"$$/ --spider\"/g' .config
- touch $@
-
-_source-check: .config.check
+_source-check: WGET += --spider
+_source-check:
$(MAKE) source
That is, the wget option '--spider' will be used _only_ by target
'_source-check' and the '.config' won't have to be edited behind one's
back.
--
Cristian
prev parent reply other threads:[~2007-07-15 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 4:59 [Buildroot] svn commit: trunk/buildroot/package/hostap ulf at uclibc.org
2007-07-09 8:18 ` Cristian Ionescu-Idbohrn
2007-07-09 9:13 ` Bernhard Fischer
2007-07-09 9:32 ` Cristian Ionescu-Idbohrn
2007-07-09 9:40 ` Bernhard Fischer
2007-07-09 10:01 ` Cristian Ionescu-Idbohrn
2007-07-09 10:23 ` [Buildroot] make source-check Bernhard Fischer
2007-07-15 12:41 ` Cristian Ionescu-Idbohrn [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=0707151431170.6891@somehost \
--to=cristian.ionescu-idbohrn@axis.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.