6 select KERNEL_SUPPORTS_SHARED_LIBS
8 Build a toolchain targeting systems running Linux as a kernel.
12 prompt "Get kernel headers from:"
14 config KERNEL_LINUX_INSTALL
16 prompt "kernel's 'headers_install'"
18 This will make use of the new headers_install rule in recent kernels.
19 This is most probably what you want to use.
21 if KERNEL_LINUX_INSTALL
23 config KERNEL_LINUX_INSTALL_CHECK
25 prompt "Check installed headers"
28 If you are in doubt that installed headers are buggy, say 'Y'
29 here to have an extra check passed onto the headers.
33 prompt "Linux kernel version"
34 # Don't remove next line
35 # CT_INSERT_VERSION_BELOW
37 config KERNEL_V_2_6_33
41 config KERNEL_V_2_6_32_9
45 config KERNEL_V_2_6_31_12
49 config KERNEL_V_2_6_30_10
53 config KERNEL_V_2_6_29_6
55 prompt "2.6.29.6 (OBSOLETE)"
58 config KERNEL_V_2_6_28_10
60 prompt "2.6.28.10 (OBSOLETE)"
63 config KERNEL_V_2_6_27_45
65 prompt "2.6.27.45 (long-term stable)"
67 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
68 It is intended to fill the niche for users who are not using distribution
69 kernels but want to use a regression-free kernel for a longer time.
71 Critical bug fixes to later 2.6 releases are often ported to this branch
72 which makes 2.6.27 a very useful base for many embedded developers seeking
73 stable APIs or those who do not need the latest bleeding edge features.
75 ... and no, this kernel has not undergone any specific QA testing.
77 See the original announcement by Adrian Bunk in the following mailing list
78 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
84 # Don't remove next line
85 # CT_INSERT_VERSION_STRING_BELOW
86 default "2.6.33" if KERNEL_V_2_6_33
87 default "2.6.32.9" if KERNEL_V_2_6_32_9
88 default "2.6.31.12" if KERNEL_V_2_6_31_12
89 default "2.6.30.10" if KERNEL_V_2_6_30_10
90 default "2.6.29.6" if KERNEL_V_2_6_29_6
91 default "2.6.28.10" if KERNEL_V_2_6_28_10
92 default "2.6.27.45" if KERNEL_V_2_6_27_45
96 prompt "Kernel verbosity:"
97 default KERNEL_LINUX_VERBOSITY_0
99 config KERNEL_LINUX_VERBOSITY_0
103 Print simplified command lines.
105 config KERNEL_LINUX_VERBOSITY_1
107 prompt "Full commands"
109 Print full command lines.
111 config KERNEL_LINUX_VERBOSITY_2
113 prompt "Exec reasons"
115 Print the reasons why a make target is rebuild.
119 config KERNEL_LINUX_VERBOSE_LEVEL
121 default 0 if KERNEL_LINUX_VERBOSITY_0
122 default 1 if KERNEL_LINUX_VERBOSITY_1
123 default 2 if KERNEL_LINUX_VERBOSITY_2
127 config KERNEL_LINUX_USE_CUSTOM_HEADERS
129 prompt "Use custom headers"
131 If you have some kernel headers lying around, you can enter the path
134 if KERNEL_LINUX_USE_CUSTOM_HEADERS
136 config KERNEL_LINUX_CUSTOM_IS_TARBALL
138 prompt "This is a tarball"
141 If you say 'n' here, the path below is expected to point to a directory
142 containing readily prepared headers
144 If you say 'y' here, then the path below is expected to point to a
145 tarball of such a directory.
147 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
148 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
150 Now, passing a tarball around is easier than passing a directory, so
151 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
152 say 'y' here, and enter the path to this tarball below.
154 config KERNEL_LINUX_CUSTOM_PATH
156 prompt "Path to custom headers directory/tarball"
158 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
160 endif # KERNEL_LINUX_USE_CUSTOM_DIR