From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: sw@weilnetz.de, qemu-devel@nongnu.org
Subject: [Qemu-devel] PO makefile rules touching source
Date: Thu, 6 Aug 2015 12:54:51 +0100 [thread overview]
Message-ID: <20150806115451.GA7242@work-vm> (raw)
Hi Stefan,
I don't really understand the way PO stuff is supposed to work,
but I often get the problem that my git tree gets changed during
an out of tree build, causing the po subdirectory to be
dirtied.
I think this is due to the rule:
$(PO_PATH)/%.po: $(PO_PATH)/messages.po
$(call quiet-command, msgmerge -q $@ $< > $@.bak && mv $@.bak $@, " GEN $@")
in po/Makefile.
Why does that merge into $(PO_PATH)/%.po rather than %.po - i.e.
why to the source rather than to the build directory?
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2015-08-06 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:54 Dr. David Alan Gilbert [this message]
2015-08-06 17:14 ` [Qemu-devel] PO makefile rules touching source Stefan Weil
2015-08-06 17:34 ` Peter Maydell
2015-08-07 9:09 ` Dr. David Alan Gilbert
2015-08-07 9:30 ` Fam Zheng
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=20150806115451.GA7242@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.