From: Andi Kleen <andi@firstfloor.org>
To: linux-kbuild@vger.kernel.org, sam@ravnborg.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] [2/3] KBUILD: Add a symlink to the source for separate objdirs
Date: Sat, 3 Jan 2009 03:21:42 +0100 (CET) [thread overview]
Message-ID: <20090103022142.684153E6651@basil.firstfloor.org> (raw)
In-Reply-To: <20090103321.351399938@firstfloor.org>
I have some scripts which need to map back to the source directory
from an objdir. This was so far done by parsing the Makefile,
but the Makefile format changes occasionally and breaks my scripts
then.
To make this more reliable add a "source" symlink back.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
Makefile | 1 +
1 file changed, 1 insertion(+)
Index: linux-2.6.28-kbuild/Makefile
===================================================================
--- linux-2.6.28-kbuild.orig/Makefile 2008-12-27 16:45:43.000000000 +0100
+++ linux-2.6.28-kbuild/Makefile 2008-12-31 20:26:27.000000000 +0100
@@ -936,6 +936,7 @@
mkdir -p include2; \
ln -fsn $(srctree)/include/asm-$(SRCARCH) include2/asm; \
fi
+ ln -fsn $(srctree) source
endif
# prepare2 creates a makefile if using a separate output directory
next prev parent reply other threads:[~2009-01-03 2:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 2:21 [PATCH] [1/3] KBUILD: Add script to manipulate .config files on the command line Andi Kleen
2009-01-03 2:21 ` Andi Kleen [this message]
2009-01-07 20:29 ` [PATCH] [2/3] KBUILD: Add a symlink to the source for separate objdirs Sam Ravnborg
2009-01-03 2:21 ` [PATCH] [3/3] KBUILD: Add a "bin" symlink for the scripts directory too Andi Kleen
2009-01-07 20:27 ` Sam Ravnborg
2009-01-07 21:30 ` Andi Kleen
2009-01-07 21:36 ` Sam Ravnborg
2009-01-03 10:54 ` [PATCH] [1/3] KBUILD: Add script to manipulate .config files on the command line Arnd Bergmann
2009-01-03 17:12 ` Andi Kleen
2009-01-07 20:18 ` Sam Ravnborg
2009-01-07 21:33 ` Andi Kleen
2009-01-07 22:07 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090103022142.684153E6651@basil.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.