qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH v2] Force object directory use
Date: Wed, 17 Nov 2010 17:57:55 -0600	[thread overview]
Message-ID: <4CE46C03.8060407@codemonkey.ws> (raw)
In-Reply-To: <4CE459B8.7050204@redhat.com>

On 11/17/2010 04:39 PM, Paolo Bonzini wrote:
> On 11/17/2010 09:08 PM, Blue Swirl wrote:
>> It's not simplification but to unify the build system. Some people
>> make changes to Makefiles and then test their changes without an
>> object directory, these may then break the build for those who use it.
>> This has happened several times already. Hopefully we can avoid those
>> breakages with this change.
>
> It happens very rarely, and the last time it was because the wrong 
> patch was committed IIUC.  It may be unified but it's pretty much 
> unlike every other build system I've ever seen.

It's not that atypical.

Keep in mind, we already create per-target build directories and use 
them.  Building the rest of the objects in a different directory isn't 
really all that bizarre.

Regards,

Anthony Liguori

> Paolo
>

      parent reply	other threads:[~2010-11-17 23:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 19:15 [Qemu-devel] [PATCH v2] Force object directory use Blue Swirl
2010-11-17 20:00 ` [Qemu-devel] " Paolo Bonzini
2010-11-17 20:08   ` Blue Swirl
2010-11-17 22:39     ` Paolo Bonzini
2010-11-17 23:05       ` Peter Maydell
2010-11-17 23:51         ` Paolo Bonzini
2010-11-17 23:57       ` Anthony Liguori [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=4CE46C03.8060407@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.com \
    --cc=pbonzini@redhat.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).