qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Yang <weiyang@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Richard Yang <weiyang@linux.vnet.ibm.com>,
	Wei Yang <weiyang.kernel@gmail.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] one question on the makefile
Date: Tue, 12 Jun 2012 21:26:18 +0800	[thread overview]
Message-ID: <20120612132618.GA2824@richard> (raw)
In-Reply-To: <4FD702D9.8060204@redhat.com>

On Tue, Jun 12, 2012 at 10:50:33AM +0200, Paolo Bonzini wrote:
>Il 12/06/2012 10:33, Wei Yang ha scritto:
>> .PHONY: $(patsubst %, check-qtest-%, $(QTEST_TARGETS))
>> $(patsubst %, check-qtest-%, $(QTEST_TARGETS)): check-qtest-%: $(check-qtest-y)
>> 	$(call quiet-command,QTEST_QEMU_BINARY=$*-softmmu/qemu-system-$* \
>> 		gtester $(GTESTER_OPTIONS) -m=$(SPEED) $(check-qtest-$*-y),"GTESTER $@")
>> 
>> I know the general idea is to create a rule for target such as
>> check-qtest-x86_64.
>> 
>> There are two colons, usually there is one colon in dependency.
>
>Search for "Static pattern rules".  Static pattern rules are probably
>the single most useful GNU make extension.  They greatly limit the
>amount of "magic" the make does, so the resulting Makefiles are more
>easily debuggable.  Here is an extract from the GNU make manual:
>
>=====
>     TARGETS ...: TARGET-PATTERN: PREREQ-PATTERNS ...
>             RECIPE
>             ...
>
>The TARGETS list specifies the targets that the rule applies to.  The
>targets can contain wildcard characters, just like the targets of
>ordinary rules (*note Using Wildcard Characters in File Names:
>Wildcards.).
>
>   The TARGET-PATTERN and PREREQ-PATTERNS say how to compute the
>prerequisites of each target.  Each target is matched against the
>TARGET-PATTERN to extract a part of the target name, called the "stem".
>This stem is substituted into each of the PREREQ-PATTERNS to make the
>prerequisite names (one from each PREREQ-PATTERN).
>=====
>
>
>$* is also replaced by the stem.  In fact in this case, the stem is not
>used in the PREREQ-PATTERNS, it is only used in the commands.
>
>Paolo
Thanks :)
I learn it. 

-- 
Richard Yang
Help you, Help me

      reply	other threads:[~2012-06-12 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12  8:33 [Qemu-devel] one question on the makefile Wei Yang
2012-06-12  8:50 ` Paolo Bonzini
2012-06-12 13:26   ` Richard Yang [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=20120612132618.GA2824@richard \
    --to=weiyang@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weiyang.kernel@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).