From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MOwLi-0008Ef-OW for qemu-devel@nongnu.org; Thu, 09 Jul 2009 12:19:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOwLe-0008D9-6S for qemu-devel@nongnu.org; Thu, 09 Jul 2009 12:19:54 -0400 Received: from [199.232.76.173] (port=34510 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOwLe-0008D5-28 for qemu-devel@nongnu.org; Thu, 09 Jul 2009 12:19:50 -0400 Received: from mx20.gnu.org ([199.232.41.8]:24961) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MOwLd-0006kD-KH for qemu-devel@nongnu.org; Thu, 09 Jul 2009 12:19:49 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MOwLc-0004os-Dd for qemu-devel@nongnu.org; Thu, 09 Jul 2009 12:19:48 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Re: [PATCH] Drop roms from standard build Date: Thu, 9 Jul 2009 17:19:43 +0100 References: <4A559842.7000404@web.de> <4A560FE7.4030906@us.ibm.com> In-Reply-To: <4A560FE7.4030906@us.ibm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907091719.44828.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Anthony Liguori , Jan Kiszka , Alexander Graf On Thursday 09 July 2009, Anthony Liguori wrote: > Jan Kiszka wrote: > > There is no point in generating and copying the optionsrom each time > > qemu is build. It's a maintenance task given that we carry them as > > binaries already. And that task could also be triggered explicitly via > > 'make roms'. Solves the mingw32 build breakage, too. > > Yeah, it needs fixing but we absolutely want to build the roms as part > of the normal build process. I disagree. For the most part I'd expect roms to be better maintained as a side project. > When a user types make install from a source tarball, if they have the > proper tool chain, we should be building everything from scratch and > installing the versions that we built. I think the chances of the user having appropriate toolchains readily available (without significant additional per-rom configury) are extremely slim. Paul