summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichal Marek2014-07-02 14:28:26 +0200
committerMichal Marek2014-07-03 15:25:11 +0200
commitc2e28dc975ea87feed84415006ae143424912ac7 (patch)
tree413a5d0f1c264b6fdbd0d8cd63adae0f691b0c43
parentkbuild: fix a typo in a kbuild document (diff)
downloadkernel-qcow2-linux-c2e28dc975ea87feed84415006ae143424912ac7.tar.gz
kernel-qcow2-linux-c2e28dc975ea87feed84415006ae143424912ac7.tar.xz
kernel-qcow2-linux-c2e28dc975ea87feed84415006ae143424912ac7.zip
kbuild: Print the name of the build directory
With commit 9da0763b (kbuild: Use relative path when building in a subdir of the source tree), the compiler messages include relative paths. These are however relative to the build directory, not the directory where make was started. Print the "Entering directory ..." message once, so that IDEs/editors can find the source files. Acked-by: David Howells <dhowells@redhat.com> Signed-off-by: Michal Marek <mmarek@suse.cz>
-rw-r--r--Makefile3
1 files changed, 3 insertions, 0 deletions
diff --git a/Makefile b/Makefile
index 97b286128c1e..40544a0babdc 100644
--- a/Makefile
+++ b/Makefile
@@ -126,7 +126,10 @@ PHONY += $(MAKECMDGOALS) sub-make
$(filter-out _all sub-make $(CURDIR)/Makefile, $(MAKECMDGOALS)) _all: sub-make
@:
+# Fake the "Entering directory" message once, so that IDEs/editors are
+# able to understand relative filenames.
sub-make: FORCE
+ @echo "make[1]: Entering directory \`$(KBUILD_OUTPUT)'"
$(if $(KBUILD_VERBOSE:1=),@)$(MAKE) -C $(KBUILD_OUTPUT) \
KBUILD_SRC=$(CURDIR) \
KBUILD_EXTMOD="$(KBUILD_EXTMOD)" -f $(CURDIR)/Makefile \