From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lx6GL-0002Yv-CQ for qemu-devel@nongnu.org; Thu, 23 Apr 2009 17:15:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lx6GF-0002Yi-U2 for qemu-devel@nongnu.org; Thu, 23 Apr 2009 17:15:16 -0400 Received: from [199.232.76.173] (port=46936 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lx6GF-0002Yf-LG for qemu-devel@nongnu.org; Thu, 23 Apr 2009 17:15:11 -0400 Received: from wf-out-1314.google.com ([209.85.200.173]:64167) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lx6GF-0002Kl-Ad for qemu-devel@nongnu.org; Thu, 23 Apr 2009 17:15:11 -0400 Received: by wf-out-1314.google.com with SMTP id 26so690809wfd.4 for ; Thu, 23 Apr 2009 14:15:10 -0700 (PDT) Message-ID: <49F0DA5A.8090400@codemonkey.ws> Date: Thu, 23 Apr 2009 16:15:06 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [7234] Use a more natural order References: <20090423185308.GH3795@csclub.uwaterloo.ca> <20090423191040.GI3795@csclub.uwaterloo.ca> <5d6222a80904231215p62c6594asc50230b252e892aa@mail.gmail.com> <49F0C826.4060503@codemonkey.ws> <20090423195902.GN3795@csclub.uwaterloo.ca> <49F0C9AA.1070703@codemonkey.ws> <20090423205431.GO3795@csclub.uwaterloo.ca> In-Reply-To: <20090423205431.GO3795@csclub.uwaterloo.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Lennart Sorensen Cc: Blue Swirl , Glauber Costa , qemu-devel@nongnu.org Lennart Sorensen wrote: > On Thu, Apr 23, 2009 at 03:03:54PM -0500, Anthony Liguori wrote: > >> I was obviously referring to posting to the mailing list. I have a set >> of compilation and unit tests that get run before every commit. >> >> There are a lot of possible configuration options for QEMU. Sometimes >> the build breaks for some combination of configuration options and this >> is a difficult thing to address in a robust way. With a patch series, >> my scripts run through what I consider the most common set of >> configurations for each patch. Right now, it usually takes a good 30 >> minutes to go through a large series just to compile test with my >> default configurations. >> > > Isn't there a configure option for building for all available targets? > Building all targets is easy. It's the various combinations of other options that get you. It's building for Linux, win32, x86, PPC, with AIO, without AIO, with KVM, without KVM, etc. > 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. > A great deal of our objects are target specific. Almost everything depends on CONFIG_USER_ONLY too. This means that full compilation takes a very long time. Regards, Anthony Liguori