From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M5yK0-0006iM-Rw for qemu-devel@nongnu.org; Mon, 18 May 2009 04:35:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M5yJw-0006eU-Kw for qemu-devel@nongnu.org; Mon, 18 May 2009 04:35:44 -0400 Received: from [199.232.76.173] (port=42664 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M5yJw-0006e5-DB for qemu-devel@nongnu.org; Mon, 18 May 2009 04:35:40 -0400 Received: from mx2.redhat.com ([66.187.237.31]:38652) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M5yJv-0002t7-V2 for qemu-devel@nongnu.org; Mon, 18 May 2009 04:35:40 -0400 Message-ID: <4A111DCF.6040302@redhat.com> Date: Mon, 18 May 2009 11:35:27 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 3/4] Update makefile to build roms References: <1242574141-18488-1-git-send-email-aliguori@us.ibm.com> <200905172304.22687.paul@codesourcery.com> <4A109D9F.9040207@codemonkey.ws> <200905180043.43205.paul@codesourcery.com> <20090518042445.GD32609@shareable.org> <20090518082503.GA12681@kos.to> In-Reply-To: <20090518082503.GA12681@kos.to> 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: Riku Voipio Cc: Alex Graf , Anthony Liguori , qemu-devel@nongnu.org, Dustin Kirkland Riku Voipio wrote: > This is indeed how it is done in Debian, roms are built in separate packages. > There is also the complication of building ROMs for non-native archs. > Say building openbios-sparc when building qemu on x86, or vgabios when > building qemu on ppc. Then you need a crosscompiler at hand. > > While it is not useful for distributions, making it possible to build roms as > part of qemu build process is still usefull for people hacking on qemu. > This makes sense, and git submodules support both of these modes of operation. When developing, the submodule links allow the two repositories to advance in lockstep, but you can also tag, tarball, and build each repository independently. -- error compiling committee.c: too many arguments to function