aboutsummaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorRoland McGrath <roland@redhat.com>2009-12-21 16:24:06 -0800
committerMichal Marek <mmarek@suse.cz>2010-02-02 14:33:54 +0100
commit84336466011c589b6af554f2f2f1fcfa1a5c1437 (patch)
treeea46dd245d649273c323275afb65ca83171c97ad /kernel
parent4b024242e8a4e9679fa327ea03958b89f89096c9 (diff)
downloadkernel_samsung_aries-84336466011c589b6af554f2f2f1fcfa1a5c1437.zip
kernel_samsung_aries-84336466011c589b6af554f2f2f1fcfa1a5c1437.tar.gz
kernel_samsung_aries-84336466011c589b6af554f2f2f1fcfa1a5c1437.tar.bz2
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>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions