crosstool-ng/config/kernel/linux.in

# Linux kernel options

## depends on ! ARCH_avr
## select KERNEL_SUPPORTS_SHARED_LIBS
##
## 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"
# Don't remove next line
# CT_INSERT_VERSION_BELOW

config KERNEL_V_4_1
    bool
    prompt "4.1.4 (stable)"

config KERNEL_V_4_0
    bool
    prompt "4.0.9 (EOL)"

config KERNEL_V_3_18
    bool
    prompt "3.18.19"

config KERNEL_V_3_14
    bool
    prompt "3.14.49"

config KERNEL_V_3_12
    bool
    prompt "3.12.46"

config KERNEL_V_3_10
    bool
    prompt "3.10.85"

config KERNEL_V_3_4
    bool
    prompt "3.4.108"

config KERNEL_V_3_2
    bool
    prompt "3.2.70"

config KERNEL_V_2_6_32
    bool
    prompt "2.6.32.67"
    help
 
config KERNEL_LINUX_CUSTOM
    bool
    prompt "custom tarball or directory"
    help
      Use a local tarball or local kernel directory of a complete kernel source tree.

config KERNEL_LINUX_CUSTOM_LOCATION
    string
    prompt "Path to custom source, tarball or directory"
    depends on KERNEL_LINUX_CUSTOM
    help
      Enter here the path to the tarball of your full kernel tree or
      kernel directory

endchoice

config KERNEL_VERSION
    string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
    default "4.1.4" if KERNEL_V_4_1
    default "4.0.9" if KERNEL_V_4_0
    default "3.18.19" if KERNEL_V_3_18
    default "3.14.49" if KERNEL_V_3_14
    default "3.12.46" if KERNEL_V_3_12
    default "3.10.85" if KERNEL_V_3_10
    default "3.4.108" if KERNEL_V_3_4
    default "3.2.70" if KERNEL_V_3_2
    default "2.6.32.67" 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