From: "Jiří Paleček" <jpalecek@web.de>
To: Mike Frysinger <vapier@gentoo.org>, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Support for parallel compilation
Date: Sat, 05 Dec 2009 01:03:26 +0100 [thread overview]
Message-ID: <op.u4fuf0b9u2flwt@marcela-gaxm89c> (raw)
In-Reply-To: <200912041413.11781.vapier@gentoo.org>
On Fri, 04 Dec 2009 20:13:11 +0100, Mike Frysinger <vapier@gentoo.org>
wrote:
> On Friday 04 December 2009 12:04:06 Jiri Palecek wrote:
>> -.PHONY: $(RECURSIVE_TARGETS) $(addprefix trunk-,$(RECURSIVE_TARGETS))
>> +.PHONY: $(RECURSIVE_TARGETS) $(addprefix trunk-,$(RECURSIVE_TARGETS))
>> $(foreach tgt,$(RECURSIVE_TARGETS),$(addprefix
>> trunk-subdir-$(tgt)--,$(SUBDIRS)))
>
> these foreach look like an overly complicated form of $(patsubst):
> $(patsubst %,moo_%,$(DIRS))
It may look like it, but they aren't. What you've written is a simple
addprefix, while the foreach does some for of cartesian product
($(TARGETS)x$(DIRS)).
Jiri Palecek
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-12-05 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4b1944a0.8713f30a.3b2f.4a0fSMTPIN_ADDED@mx.google.com>
2009-12-04 19:13 ` [LTP] [PATCH] Support for parallel compilation Mike Frysinger
2009-12-05 0:03 ` Jiří Paleček [this message]
2009-12-05 8:01 ` Garrett Cooper
2009-12-19 2:05 ` Jiří Paleček
2009-12-19 4:30 ` Garrett Cooper
2009-12-04 17:04 Jiri Palecek
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=op.u4fuf0b9u2flwt@marcela-gaxm89c \
--to=jpalecek@web.de \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.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