diff options
| author | Michael Marineau | 2015-08-09 09:02:55 +0200 |
|---|---|---|
| committer | Paolo Bonzini | 2015-09-09 15:34:54 +0200 |
| commit | 12a1ddc160cb6a73e8a6c319f3962a20da2cd22f (patch) | |
| tree | 8e94723d2bd220221cb19b67caae76cc7b1a31d1 /include | |
| parent | Move RAMBlock and ram_list to ram_addr.h (diff) | |
| download | qemu-12a1ddc160cb6a73e8a6c319f3962a20da2cd22f.tar.gz qemu-12a1ddc160cb6a73e8a6c319f3962a20da2cd22f.tar.xz qemu-12a1ddc160cb6a73e8a6c319f3962a20da2cd22f.zip | |
Makefile.target: include top level build dir in vpath
Using ccache with CCACHE_BASEDIR set to $(SRC_PATH) or a parent will
rewrite all absolute paths to relative paths. This interacts poorly with
QEMU's two-level build directory scheme. For example, lets say
BUILD_DIR=$(SRC_PATH)/build so build/blockdev.d will contain:
blockdev.o: ../blockdev.c ../include/sysemu/block-backend.h \
Now the target build under build/x86_64-softmmu or similar will depend
on ../blockdev.o which in turn will get make to source ../blockdev.d to
check its dependencies. Since make always considers paths relative to
the current working directory rather than the makefile the path appeared
in the relative path to ../blockdev.c is useless.
This change simply adds the top level build directory to vpath so paths
relative to the source directory, top build directory, and target build
directory all work just fine.
Signed-off-by: Michael Marineau <michael.marineau@coreos.com>
Message-Id: <1439103775-11836-1-git-send-email-michael.marineau@coreos.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions