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_32_8
41 config KERNEL_V_2_6_32_7
45 config KERNEL_V_2_6_32_6
49 config KERNEL_V_2_6_32_5
53 config KERNEL_V_2_6_32_4
57 config KERNEL_V_2_6_32_3
61 config KERNEL_V_2_6_32_2
65 config KERNEL_V_2_6_32_1
69 config KERNEL_V_2_6_32
73 config KERNEL_V_2_6_31_12
77 config KERNEL_V_2_6_30_10
81 config KERNEL_V_2_6_29_6
83 prompt "2.6.29.6 (OBSOLETE)"
86 config KERNEL_V_2_6_28_10
88 prompt "2.6.28.10 (OBSOLETE)"
91 config KERNEL_V_2_6_27_45
93 prompt "2.6.27.45 (long-term stable)"
95 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
96 It is intended to fill the niche for users who are not using distribution
97 kernels but want to use a regression-free kernel for a longer time.
99 Critical bug fixes to later 2.6 releases are often ported to this branch
100 which makes 2.6.27 a very useful base for many embedded developers seeking
101 stable APIs or those who do not need the latest bleeding edge features.
103 ... and no, this kernel has not undergone any specific QA testing.
105 See the original announcement by Adrian Bunk in the following mailing list
106 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
110 config KERNEL_VERSION
112 # Don't remove next line
113 # CT_INSERT_VERSION_STRING_BELOW
114 default "2.6.32.8" if KERNEL_V_2_6_32_8
115 default "2.6.32.7" if KERNEL_V_2_6_32_7
116 default "2.6.32.6" if KERNEL_V_2_6_32_6
117 default "2.6.32.5" if KERNEL_V_2_6_32_5
118 default "2.6.32.4" if KERNEL_V_2_6_32_4
119 default "2.6.32.3" if KERNEL_V_2_6_32_3
120 default "2.6.32.2" if KERNEL_V_2_6_32_2
121 default "2.6.32.1" if KERNEL_V_2_6_32_1
122 default "2.6.32" if KERNEL_V_2_6_32
123 default "2.6.31.12" if KERNEL_V_2_6_31_12
124 default "2.6.30.10" if KERNEL_V_2_6_30_10
125 default "2.6.29.6" if KERNEL_V_2_6_29_6
126 default "2.6.28.10" if KERNEL_V_2_6_28_10
127 default "2.6.27.45" if KERNEL_V_2_6_27_45
131 prompt "Kernel verbosity:"
132 default KERNEL_LINUX_VERBOSITY_0
134 config KERNEL_LINUX_VERBOSITY_0
138 Print simplified command lines.
140 config KERNEL_LINUX_VERBOSITY_1
142 prompt "Full commands"
144 Print full command lines.
146 config KERNEL_LINUX_VERBOSITY_2
148 prompt "Exec reasons"
150 Print the reasons why a make target is rebuild.
154 config KERNEL_LINUX_VERBOSE_LEVEL
156 default 0 if KERNEL_LINUX_VERBOSITY_0
157 default 1 if KERNEL_LINUX_VERBOSITY_1
158 default 2 if KERNEL_LINUX_VERBOSITY_2
162 config KERNEL_LINUX_USE_CUSTOM_HEADERS
164 prompt "Use custom headers"
166 If you have some kernel headers lying around, you can enter the path
169 if KERNEL_LINUX_USE_CUSTOM_HEADERS
171 config KERNEL_LINUX_CUSTOM_IS_TARBALL
173 prompt "This is a tarball"
176 If you say 'n' here, the path below is expected to point to a directory
177 containing readily prepared headers
179 If you say 'y' here, then the path below is expected to point to a
180 tarball of such a directory.
182 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
183 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
185 Now, passing a tarball around is easier than passing a directory, so
186 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
187 say 'y' here, and enter the path to this tarball below.
189 config KERNEL_LINUX_CUSTOM_PATH
191 prompt "Path to custom headers directory/tarball"
193 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
195 endif # KERNEL_LINUX_USE_CUSTOM_DIR