Re: [Qemu-devel] [PATCH v3 00/11] qapi: add support for lists of native types

[mdroth <mdroth@linux.vnet.ibm.com>]

On Thu, May 16, 2013 at 12:38:30PM +0200, Laszlo Ersek wrote:
> On 05/15/13 21:13, mdroth wrote:
> > On Wed, May 15, 2013 at 02:05:58PM -0400, Luiz Capitulino wrote:
> >> On Wed, 15 May 2013 12:42:24 -0500
> >> mdroth <mdroth@linux.vnet.ibm.com> wrote:
> 
> >>> The only way I've managed to reproduce this is by having a stale
> >>> qapi-types.h hanging around in $SRC_DIR while i'm building in a
> >>> different $BUILD_DIR. Can you confirm that's not what's happening here?
> >>
> >> Yes, it was :( I had an old qapi-types.h in $SRC_DIR, but was building
> >> in a different $BUILD_DIR. I am really sorry for having wasted your time
> >> on this.
> >>
> >> I've applied this series to qmp-next branch, but I have no idea how I ended
> >> up with a qapi-types.h file in $SRC_DIR. I have an alias to build qemu that
> >> I use for several months now...
> >>
> > 
> > No problem, only thought to check that scenario because it happens to me
> > all the time :)
> 
> Side question: what's a common use case for a separate $BUILD_DIR? I
> just use "git clean -fdx" in $SRC_DIR instead of "make clean". The need
> to reconfigure (and to regenerate my tags file from scratch) is a small
> price to pay for the peace of mind.

I also do it for peace of mind, but I'm not particularly disciplined about
logging all my changes/new files into git as i go, so it's nice to be able to
do a clean build even when my $SRC_DIR is littered with abandoned
code/files/etc by simply wiping out the build dir.

I also have a number of situations where the resulting builds need to
be kept around for a while. For example I have build directories for
v1.1->v1.5 that I keep around for migration testing, other builds
for general usage, and a multitude of temp builds i might create to
compare upstream against a test/stable/development build. I could
use `make install` with an install prefix for this but for me it's quicker
to just use the binaries within the build directory.

Wasn't aware of `git clean` though, always just tried to make
due with `git reset --hard` + rm but that can get tedious at times.

> 
> Thanks
> Laszlo
>