diff options
| author |   Bryan Hundven <bryanhundven@gmail.com> | 2015-11-26 11:43:03 (GMT) |
|---|---|---|
| committer | Bryan Hundven <bryanhundven@gmail.com> | 2015-12-08 15:20:35 (GMT) |
| commit | 5d967e8b3949db7f4b8dae31e2f0b14efc568de9 (patch) | |
| tree | 672648629e861162475e1183b25ec2bfd7627965 /config/kernel/linux.in | |
| parent | 9d835eddcf8b225bafbeacafaa8db830b201b5c9 (diff) | |
Linux: Remove obsolete Linux custom headers
This option allowed you to use a custom headers directory/tarball to use
in your sysroot.
Not to be confused with using a custom source, that option is the
preferred method.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Diffstat (limited to 'config/kernel/linux.in')
| -rw-r--r-- | config/kernel/linux.in | 45 |
1 files changed, 0 insertions, 45 deletions
diff --git a/config/kernel/linux.in b/config/kernel/linux.in index 3d919df..5b429ec 100644 --- a/config/kernel/linux.in +++ b/config/kernel/linux.in @@ -5,22 +5,6 @@ ## ## help Build a toolchain targeting systems running Linux as a kernel. -config KERNEL_LINUX_USE_CUSTOM_HEADERS - bool - prompt "Use pre-installed headers tree (OBSOLETE)" - depends on OBSOLETE - help - If you have some pre-installed kernel headers lying around, you can - enter the path to these headers, below, they will be copied from - there, and into the toolchain's sysroot. - - Note: - This will *not* let you use a complete kernel tree! - If you want to use your own full kernel tree, then you want to say 'N' - here, and select KERNEL_LINUX_CUSTOM, in the versions list, below. - -if ! KERNEL_LINUX_USE_CUSTOM_HEADERS - choice bool prompt "Linux kernel version" @@ -99,32 +83,3 @@ config KERNEL_VERSION default "3.2.72" if KERNEL_V_3_2 default "2.6.32.68" if KERNEL_V_2_6_32 default "custom" if KERNEL_LINUX_CUSTOM - -endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS - -if KERNEL_LINUX_USE_CUSTOM_HEADERS - -config KERNEL_LINUX_CUSTOM_PATH - string - prompt "Path to custom headers directory/tarball" - help - See KERNEL_LINUX_CUSTOM_IS_TARBALL, below. - -config KERNEL_LINUX_CUSTOM_IS_TARBALL - bool - prompt "This is a tarball" - help - If you say 'n' here, the path above is expected to point to a directory - containing readily prepared headers - - If you say 'y' here, then the path above is expected to point to a - tarball of such a directory. - - Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include, - say 'n' here, and enter: /foo/bar/buz/my_hdrs below. - - Now, passing a tarball around is easier than passing a directory, so - if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include, - say 'y' here, and enter the path to this tarball below. - -endif # KERNEL_LINUX_USE_CUSTOM_HEADERS |