From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1InMeI-0004fx-TR for qemu-devel@nongnu.org; Wed, 31 Oct 2007 19:06:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1InMeH-0004cd-9c for qemu-devel@nongnu.org; Wed, 31 Oct 2007 19:06:58 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1InMeH-0004cH-5U for qemu-devel@nongnu.org; Wed, 31 Oct 2007 19:06:57 -0400 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 1InMeG-0006l5-Iy for qemu-devel@nongnu.org; Wed, 31 Oct 2007 19:06:56 -0400 Date: Wed, 31 Oct 2007 23:06:50 +0000 From: Thiemo Seufer Subject: Re: [Qemu-devel] How to split vl.h Message-ID: <20071031230649.GL7712@networkno.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel Blue Swirl wrote: > Hi, > > With the automatic dependency rule installed, modifying vl.h causes > all files to be recompiled. This is of course the correct action, but > it's a major slowdown for development too. > > How should we split vl.h into smaller pieces? Give each device a > header file, like m48t59? Functions which are only called from below /hw should go in /hw/.h, other device stuff should probably go in a separate toplevel header, maybe hw.h. That way we get something which could evolve in the interface of a hw-library in future. > What about other stuff exported from vl.c? I think the best answer is to cut vl.c in logical chunks before starting to split vl.h further. Thiemo