cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: cpufreq@vger.kernel.org
Cc: Franck Bui-Huu <fbuihuu@gmail.com>,
	Dominik Brodowski <linux@dominikbrodowski.net>
Subject: [PATCH 09/13] cpupower tool: makefile: simplify the recipe used to generate cpupower.pot target
Date: Sun, 25 Mar 2012 20:38:50 +0200	[thread overview]
Message-ID: <1332700734-26435-9-git-send-email-linux@dominikbrodowski.net> (raw)
In-Reply-To: <1332700734-26435-1-git-send-email-linux@dominikbrodowski.net>

From: Franck Bui-Huu <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>
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
---
 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 eb7f448..1952605 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.5.4


  parent reply	other threads:[~2012-03-25 18:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 18:38 [git pull] cpupowerutils updates for 3.4 Dominik Brodowski
2012-03-25 18:38 ` [PATCH 01/13] cpupower: Better interface for accessing AMD pci registers Dominik Brodowski
2012-03-25 18:38   ` [PATCH 02/13] cpupower: AMD fam14h/Ontario monitor can also be used by fam12h cpus Dominik Brodowski
2012-03-25 18:38   ` [PATCH 03/13] cpupower: Add cpupower-idle-info manpage Dominik Brodowski
2012-03-25 18:38   ` [PATCH 04/13] cpupower: Unify cpupower-frequency-* manpages Dominik Brodowski
2012-03-25 18:38   ` [PATCH 05/13] cpupower: Fix number of idle states Dominik Brodowski
2012-03-25 18:38   ` [PATCH 06/13] cpupower: Remove unneeded code and by that fix a memleak Dominik Brodowski
2012-03-25 18:38   ` [PATCH 07/13] cpupower: Fix linking with --as-needed Dominik Brodowski
2012-03-25 18:38   ` [PATCH 08/13] cpupower tool: remove use of undefined variables from the clean target of the top makefile Dominik Brodowski
2012-03-25 18:38   ` Dominik Brodowski [this message]
2012-03-25 18:38   ` [PATCH 10/13] cpupower tool: allow to build in a separate directory Dominik Brodowski
2012-03-25 18:38   ` [PATCH 11/13] cpupower: Fix broken mask values Dominik Brodowski
2012-03-25 18:38   ` [PATCH 12/13] cpupower tools: allow to build debug tools in a separate directory too Dominik Brodowski
2012-03-25 18:38   ` [PATCH 13/13] cpupower tools: add install target to the debug tools' makefiles Dominik Brodowski
2012-03-29  5:23 ` [git pull] cpupowerutils updates for 3.4 Dominik Brodowski

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=1332700734-26435-9-git-send-email-linux@dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --cc=cpufreq@vger.kernel.org \
    --cc=fbuihuu@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).