From: Franck Bui-Huu <fbuihuu@gmail.com>
To: linux@dominikbrodowski.net
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] cpupower tool: makefile: simplify the recipe used to generate cpupower.pot target
Date: Wed, 1 Feb 2012 12:08:19 +0100 [thread overview]
Message-ID: <1328094500-19393-3-git-send-email-fbuihuu@gmail.com> (raw)
In-Reply-To: <1328094500-19393-1-git-send-email-fbuihuu@gmail.com>
Use the '-p' and '-o' switches to specify the pathname of the output
file to xgettext(1). This avoids to move manually the output file if
xgettext(1) succeeds.
Signed-off-by: Franck Bui-Huu <fbuihuu@gmail.com>
---
tools/power/cpupower/Makefile | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/tools/power/cpupower/Makefile b/tools/power/cpupower/Makefile
index b7d87af..f1fe491 100644
--- a/tools/power/cpupower/Makefile
+++ b/tools/power/cpupower/Makefile
@@ -199,9 +199,7 @@ cpupower: $(UTIL_OBJS) libcpupower.so.$(LIB_MAJ)
po/$(PACKAGE).pot: $(UTIL_SRC)
$(ECHO) " GETTEXT " $@
$(QUIET) xgettext --default-domain=$(PACKAGE) --add-comments \
- --keyword=_ --keyword=N_ $(UTIL_SRC) && \
- test -f $(PACKAGE).po && \
- mv -f $(PACKAGE).po po/$(PACKAGE).pot
+ --keyword=_ --keyword=N_ $(UTIL_SRC) -p $(@D) -o $(@F)
po/%.gmo: po/%.po
$(ECHO) " MSGFMT " $@
--
1.7.7.4
next prev parent reply other threads:[~2012-02-01 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 11:08 [PATCH 0/3] cpupower tool: allow building output to be in a separate directory Franck Bui-Huu
2012-02-01 11:08 ` [PATCH 1/3] cpupower tool: remove use of undefined variables from the clean target of the top makefile Franck Bui-Huu
2012-02-01 11:08 ` Franck Bui-Huu [this message]
2012-02-01 11:08 ` [PATCH 3/3] cpupower tool: allow to build in a separate directory Franck Bui-Huu
2012-02-05 20:32 ` [PATCH 0/3] cpupower tool: allow building output to be " Dominik Brodowski
2012-02-06 10:45 ` Franck Bui-Huu
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=1328094500-19393-3-git-send-email-fbuihuu@gmail.com \
--to=fbuihuu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.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 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).