kconfig CROSS_COMPILE option

This adds CROSS_COMPILE as a kconfig string so you can store it in
.config.  Then you can use plain "make" in the configured kernel build
directory to do the right cross compilation without setting the
command-line or environment variable every time.

With this, you can set up different build directories for different kernel
configurations, whether native or cross-builds, and then use the simple:

	make -C /build/dir M=module-source-dir

idiom to build modules for any given target kernel, indicating which one
by nothing but the build directory chosen.

I tried a version that defaults the string with env="CROSS_COMPILE" so
that in a "make oldconfig" with CROSS_COMPILE in the environment you can
just hit return to store the way you're building it.  But the kconfig
prompt for strings doesn't give you any way to say you want an empty
string instead of the default, so I punted that.

Signed-off-by: Roland McGrath <roland@redhat.com>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Anibal Monsalve Salazar <anibal@debian.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Michal Marek <mmarek@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Michal Marek <mmarek@suse.cz>

1 files changed, 8 insertions, 0 deletions

diff --git a/init/Kconfig b/init/Kconfig
index d95ca7cd5d45..313506d8be6e 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -76,6 +76,14 @@ config INIT_ENV_ARG_LIMIT
           variables passed to init from the kernel command line.
 
 
+config CROSS_COMPILE
+        string "Cross-compiler tool prefix"
+        help
+          Same as running 'make CROSS_COMPILE=prefix-' but stored for
+          default make runs in this kernel build directory.  You don't
+          need to set this unless you want the configured kernel build
+          directory to select the cross-compiler automatically.
+
 config LOCALVERSION
         string "Local version - append to kernel release"
         help