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