From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iop3D-0002ev-Uu for qemu-devel@nongnu.org; Sun, 04 Nov 2007 18:38:44 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iop3A-0002bj-Oy for qemu-devel@nongnu.org; Sun, 04 Nov 2007 18:38:43 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iop3A-0002bb-DI for qemu-devel@nongnu.org; Sun, 04 Nov 2007 18:38:40 -0500 Received: from relay01.mx.bawue.net ([193.7.176.67]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Iop3A-0005h0-C4 for qemu-devel@nongnu.org; Sun, 04 Nov 2007 18:38:40 -0500 Date: Sun, 4 Nov 2007 23:38:34 +0000 From: Thiemo Seufer Subject: Re: [Qemu-devel] How to split vl.h Message-ID: <20071104233834.GH9363@networkno.de> References: <200711041754.55320.paul@codesourcery.com> <1194205288.31210.47.camel@rapid> <200711042130.20231.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200711042130.20231.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: Blue Swirl , "J. Mayer" , qemu-devel@nongnu.org Paul Brook wrote: > > > I not sure a single hw/hw.h file will give any benefit because there's a > > > fair amount of interfacing between the target devices emulation and the > > > host side interaction code. i.e. there's not much that's only used inside > > > hw/. hw/ is about as big as most of the rest of qemu put together, so > > > splitting that is probably going to get the biggest wins. > > > > hw library contains a lot of code but is not all is compiled for all > > targets. > > *shrug*. When I'm developing I generally only build the target I'm interested > in anyway. If I'm doing a verification build before committing I'll build > from scratch anyway. I've been bitten by faulty dependency checking > (automatic or otherwise) often enough that I don't trust it for anything > important. Dependency checking appears to work well now. Thiemo