summaryrefslogtreecommitdiff
path: root/config
diff options
context:
space:
mode:
Diffstat (limited to 'config')
-rw-r--r--config/kernel/linux.in35
1 files changed, 26 insertions, 9 deletions
diff --git a/config/kernel/linux.in b/config/kernel/linux.in
index c5b8752..2dcb34b 100644
--- a/config/kernel/linux.in
+++ b/config/kernel/linux.in
@@ -286,20 +286,37 @@ endif
config KERNEL_LINUX_USE_CUSTOM_DIR
bool
- prompt "Use custom directory"
+ prompt "Use custom headers"
help
If you have some kernel headers lying around, you can enter the path
below.
-config KERNEL_LINUX_CUSTOM_DIR
- string
- prompt "Where are those custom headers?"
- depends on KERNEL_LINUX_USE_CUSTOM_DIR
+if KERNEL_LINUX_USE_CUSTOM_DIR
+
+config KERNEL_LINUX_CUSTOM_IS_TARBALL
+ bool
+ prompt "This is a tarball"
+ default n
help
- Enter the base directory where the headers are to be found.
+ If you say 'n' here, the path below is expected to point to a directory
+ containing readily prepared headers
+
+ If you say 'y' here, then the path below 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.
- Eg. if the headers are in /some/place/include, then enter /some/place.
- This is the same path you entered when you typed:
- make INSTALL_HDR_PATH=/some/place headers_install
+ 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.
+
+config KERNEL_LINUX_CUSTOM_PATH
+ string
+ prompt "Path to custom headers directory/tarball"
+ help
+ See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
+
+endif # KERNEL_LINUX_USE_CUSTOM_DIR
endchoice