From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: James Hanley <jhanley@dgtlrift.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] .PO files modified under build
Date: Fri, 24 Mar 2017 11:58:31 +0000 [thread overview]
Message-ID: <20170324115830.GC16047@work-vm> (raw)
In-Reply-To: <CAF++6APQ=H6=-BmE=wJHzibKLcAGbP75FLOPJP3vX3kdeww+5Q@mail.gmail.com>
* James Hanley (jhanley@dgtlrift.com) wrote:
> I have a git clone of qemu, and I build out of qemu-build... essentially
> the layout looks like:
> ./
> ./qemu/ -> clone of qemu
> ./qemu-build/
> ./Makefile
>
> The contents of the top level Makefile contain the following rules:
> rwildcard=$(wildcard $1$2) $(foreach d,$(wildcard $1*),$(call
> rwildcard,$d/,$2))
> files := $(call rwildcard,qemu/,*.[ch])
>
> .PHONY: clean_orphan_artifacts
> clean_orphan_artifacts: $(note update)
> $(Q) \
> $(GIT_VERBOSE) ; \
> cd qemu && \
> git clean -f -d -X
> $(call trace,GIT CLEAN)
>
> qemu-build: qemu $(files) clean_orphan_artifacts
> $(Q) \
> mkdir -p $(@) && \
> cd $(@) && \
> ../qemu/configure \
> --prefix=$(current_path)/local \
> --target-list=arm-softmmu \
> --disable-werror && \
> $(MAKE) && \
> $(MAKE) install \
> $(call trace,BUILD)
>
> It seems that somehow the .po files are being modified under the qemu repo
> even though the entire build is out of ./qemu-build.
>
> The two questions are:
> Should the .po files be modified under the qemu path when building out
> of another (ie qemu-build)?
> Should the .po files continue to be versioned or placed in .gitignore if
> they are (apparently) generated?
It's a known problem we've had for ages, and IMHO really needs fixing.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2017-03-24 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 14:11 [Qemu-devel] .PO files modified under build James Hanley
2017-03-24 11:58 ` Dr. David Alan Gilbert [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=20170324115830.GC16047@work-vm \
--to=dgilbert@redhat.com \
--cc=jhanley@dgtlrift.com \
--cc=qemu-devel@nongnu.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 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.