From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ion37-0004Jh-R9
	for qemu-devel@nongnu.org; Sun, 04 Nov 2007 16:30:29 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ion35-0004H2-QO
	for qemu-devel@nongnu.org; Sun, 04 Nov 2007 16:30:29 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ion35-0004Gc-J6
	for qemu-devel@nongnu.org; Sun, 04 Nov 2007 16:30:27 -0500
Received: from mail.codesourcery.com ([65.74.133.4])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1Ion35-0000rF-2h
	for qemu-devel@nongnu.org; Sun, 04 Nov 2007 16:30:27 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] How to split vl.h
Date: Sun, 4 Nov 2007 21:30:17 +0000
References: <f43fc5580710311112o456a348foc4528f99aae6c9c@mail.gmail.com>
	<200711041754.55320.paul@codesourcery.com>
	<1194205288.31210.47.camel@rapid>
In-Reply-To: <1194205288.31210.47.camel@rapid>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200711042130.20231.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "J. Mayer" <l_indien@magic.fr>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org

> > 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.

Paul