From: Andi Kleen <andi@firstfloor.org>
To: linux-kbuild@vger.kernel.org, sam@ravnborg.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] [3/3] KBUILD: Add a "bin" symlink for the scripts directory too
Date: Sat, 3 Jan 2009 03:21:43 +0100 (CET) [thread overview]
Message-ID: <20090103022143.6D0803E6650@basil.firstfloor.org> (raw)
In-Reply-To: <20090103321.351399938@firstfloor.org>
Several of the scripts in "scripts" are useful to operate on
files in a separate objdir. Instead of always manually typing
the path to the source dir create a convenient symlink to
the source dir's script directory in the objdir too.
I named it bin because scripts was already used for the object
files of scripts.
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 2009-01-01 15:52:52.000000000 +0100
+++ linux-2.6.28-kbuild/Makefile 2009-01-01 15:53:09.000000000 +0100
@@ -937,6 +937,7 @@
ln -fsn $(srctree)/include/asm-$(SRCARCH) include2/asm; \
fi
ln -fsn $(srctree) source
+ ln -fsn $(srctree)/scripts bin
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 ` [PATCH] [2/3] KBUILD: Add a symlink to the source for separate objdirs Andi Kleen
2009-01-07 20:29 ` Sam Ravnborg
2009-01-03 2:21 ` Andi Kleen [this message]
2009-01-07 20:27 ` [PATCH] [3/3] KBUILD: Add a "bin" symlink for the scripts directory too 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=20090103022143.6D0803E6650@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.