qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Glauber Costa <glommer@gmail.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [7234] Use a more natural order
Date: Fri, 24 Apr 2009 10:18:11 +0200	[thread overview]
Message-ID: <49F175C3.3070607@redhat.com> (raw)
In-Reply-To: <20090423205431.GO3795@csclub.uwaterloo.ca>

On 04/23/09 22:54, Lennart Sorensen wrote:
> Isn't there a configure option for building for all available targets?
>
> It might take 30 minutes, but it saves large amounts of time for everyone
> else later.  Also I would hope make is smart enough to only recompile
> the bits that changed, so that shouldn't take as long.

Even picking a reasonable subset catches most of these.

/me builds i386 + x86_64 softmmu (that's what I'm working on)
also usermode variants (to catch build bugs there)
and sparc (because it has neither xen nor kvm and also is bigendian)

btw: Does qemu support compiling with separate src/obj trees?  I think 
it doesn't, but would be useful because one could easily add a mingw32 
windows cross build to the picture ...

cheers,
   Gerd

  parent reply	other threads:[~2009-04-24  8:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 18:29 [Qemu-devel] [7234] Use a more natural order Blue Swirl
2009-04-23 18:39 ` Andreas Färber
2009-04-23 18:43   ` Blue Swirl
2009-04-23 18:53 ` Lennart Sorensen
2009-04-23 19:01   ` Blue Swirl
2009-04-23 19:10     ` Lennart Sorensen
2009-04-23 19:15       ` Glauber Costa
2009-04-23 19:39         ` Blue Swirl
2009-04-23 19:59           ` Anthony Liguori
2009-04-23 20:20             ` Blue Swirl
2009-04-23 19:57         ` Anthony Liguori
2009-04-23 19:59           ` Lennart Sorensen
2009-04-23 20:03             ` Anthony Liguori
2009-04-23 20:54               ` Lennart Sorensen
2009-04-23 21:15                 ` Anthony Liguori
2009-04-23 22:13                   ` Jamie Lokier
2009-04-24  0:10                     ` Anthony Liguori
2009-04-24  8:18                 ` Gerd Hoffmann [this message]
2009-04-24 12:14                   ` Anthony Liguori
2009-04-24 12:32                   ` Stefan Weil
2009-04-23 19:31       ` Blue Swirl
2009-04-23 19:44         ` Lennart Sorensen
2009-04-23 22:46           ` Jamie Lokier
2009-04-24 18:07             ` Lennart Sorensen
2009-04-24 18:58               ` Nathan Froyd
2009-04-23 19:12   ` M. Warner Losh
2009-04-23 19:28     ` Lennart Sorensen
2009-04-23 19:41       ` M. Warner Losh
2009-04-23 19:55         ` Lennart Sorensen
2009-04-23 20:07           ` M. Warner Losh
2009-04-23 21:01             ` Lennart Sorensen
2009-04-23 23:02           ` Jamie Lokier
2009-04-23 22:52       ` Jamie Lokier
2009-04-23 19:37   ` [Qemu-devel] " Jan Kiszka
2009-04-23 19:46     ` Lennart Sorensen
2009-04-23 21:30       ` malc
2009-04-23 22:10       ` Jamie Lokier
2009-04-24  8:09   ` [Qemu-devel] " Gerd Hoffmann

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=49F175C3.3070607@redhat.com \
    --to=kraxel@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=glommer@gmail.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    --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).