From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Peter Crosthwaite <crosthwaitepeter@gmail.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Makefile.target: set master BUILD_DIR
Date: Tue, 26 May 2015 19:17:10 +0200 [thread overview]
Message-ID: <5564AA96.4010108@redhat.com> (raw)
In-Reply-To: <CAEgOgz59zK7UR3OS7x3g8vDmRBVHQ1ZJd7GTRNHr7uQPvqRuyw@mail.gmail.com>
On 26/05/2015 19:15, Peter Crosthwaite wrote:
> On Tue, May 26, 2015 at 6:29 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>>
>> On 26/05/2015 07:38, Peter Crosthwaite wrote:
>>> make can be invoked in the individual build dirs to build an individual
>>> target or just a single file of a target. e.g.
>>>
>>> touch translate-all.c
>>> make -C microblazeel-softmmu translate-all.o
>>
>> Out of curiosity, why not use "make subdir-microblazeel-softmmu" instead?
>>
>
> Does that in any way allow you to specify a single file?
>
> This come up in my multi-arch work, where I am constantly touching
> core headers while being a fully configured build. Every change
> triggers major recompilation. So to make my quick edits I have started
> a process where I use this fuller make specification to rebuild the
> one under-development file+target combo that failed until the build
> bugs go away. Then once is works I continue with unqualified build. I
> also want to avoid retrigger of the common-obj build.
Understood, thanks for the application. I'll include the patch in my
next pull request (and will prepare a public git tree sooner rather than
later).
Paolo
prev parent reply other threads:[~2015-05-26 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 5:38 [Qemu-devel] [PATCH] Makefile.target: set master BUILD_DIR Peter Crosthwaite
2015-05-26 13:29 ` Paolo Bonzini
2015-05-26 17:15 ` Peter Crosthwaite
2015-05-26 17:17 ` Paolo Bonzini [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=5564AA96.4010108@redhat.com \
--to=pbonzini@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=kraxel@redhat.com \
--cc=peter.crosthwaite@xilinx.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 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).