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
25 prompt "Linux kernel version"
26 # Don't remove next line
27 # CT_INSERT_VERSION_BELOW
29 config KERNEL_V_2_6_35
33 config KERNEL_V_2_6_34_2
37 config KERNEL_V_2_6_34_1
41 config KERNEL_V_2_6_34
45 config KERNEL_V_2_6_33_7
49 config KERNEL_V_2_6_33_6
53 config KERNEL_V_2_6_33_5
57 config KERNEL_V_2_6_33_4
61 config KERNEL_V_2_6_33_3
65 config KERNEL_V_2_6_33_2
69 config KERNEL_V_2_6_33_1
73 config KERNEL_V_2_6_33
77 config KERNEL_V_2_6_32_17
81 config KERNEL_V_2_6_31_14
85 config KERNEL_V_2_6_30_10
89 config KERNEL_V_2_6_27_49
91 prompt "2.6.27.49 (long-term stable)"
93 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
94 It is intended to fill the niche for users who are not using distribution
95 kernels but want to use a regression-free kernel for a longer time.
97 Critical bug fixes to later 2.6 releases are often ported to this branch
98 which makes 2.6.27 a very useful base for many embedded developers seeking
99 stable APIs or those who do not need the latest bleeding edge features.
101 ... and no, this kernel has not undergone any specific QA testing.
103 See the original announcement by Adrian Bunk in the following mailing list
104 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
106 config KERNEL_LINUX_CUSTOM
108 prompt "custom tarball"
110 Use a local tarball of a complete kernel source tree.
112 config KERNEL_LINUX_CUSTOM_TARBALL
114 prompt "Path to custom tarball"
115 depends on KERNEL_LINUX_CUSTOM
117 Enter here the path to the tarball of your full kernel tree.
121 config KERNEL_VERSION
123 # Don't remove next line
124 # CT_INSERT_VERSION_STRING_BELOW
125 default "2.6.35" if KERNEL_V_2_6_35
126 default "2.6.34.2" if KERNEL_V_2_6_34_2
127 default "2.6.34.1" if KERNEL_V_2_6_34_1
128 default "2.6.34" if KERNEL_V_2_6_34
129 default "2.6.33.7" if KERNEL_V_2_6_33_7
130 default "2.6.33.6" if KERNEL_V_2_6_33_6
131 default "2.6.33.5" if KERNEL_V_2_6_33_5
132 default "2.6.33.4" if KERNEL_V_2_6_33_4
133 default "2.6.33.3" if KERNEL_V_2_6_33_3
134 default "2.6.33.2" if KERNEL_V_2_6_33_2
135 default "2.6.33.1" if KERNEL_V_2_6_33_1
136 default "2.6.33" if KERNEL_V_2_6_33
137 default "2.6.32.17" if KERNEL_V_2_6_32_17
138 default "2.6.31.14" if KERNEL_V_2_6_31_14
139 default "2.6.30.10" if KERNEL_V_2_6_30_10
140 default "2.6.27.49" if KERNEL_V_2_6_27_49
144 prompt "Kernel verbosity:"
145 default KERNEL_LINUX_VERBOSITY_0
147 config KERNEL_LINUX_VERBOSITY_0
151 Print simplified command lines.
153 config KERNEL_LINUX_VERBOSITY_1
155 prompt "Full commands"
157 Print full command lines.
159 config KERNEL_LINUX_VERBOSITY_2
161 prompt "Exec reasons"
163 Print the reasons why a make target is rebuild.
167 config KERNEL_LINUX_VERBOSE_LEVEL
169 default 0 if KERNEL_LINUX_VERBOSITY_0
170 default 1 if KERNEL_LINUX_VERBOSITY_1
171 default 2 if KERNEL_LINUX_VERBOSITY_2
173 config KERNEL_LINUX_INSTALL_CHECK
175 prompt "Check installed headers"
178 If you are in doubt that installed headers are buggy, say 'Y'
179 here to have an extra check passed onto the headers.
181 endif # KERNEL_LINUX_INSTALL
183 config KERNEL_LINUX_USE_CUSTOM_HEADERS
185 prompt "pre-installed headers tree"
187 If you have some pre-installed kernel headers lying around, you can
188 enter the path to these headers, below, they will be copied from
189 there, and into the toolchain's sysroot.
192 This will *not* let you use a complete kernel tree!
193 If you want to use your own full kernel tree, then you want to
194 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
196 if KERNEL_LINUX_USE_CUSTOM_HEADERS
198 config KERNEL_LINUX_CUSTOM_IS_TARBALL
200 prompt "This is a tarball"
203 If you say 'n' here, the path below is expected to point to a directory
204 containing readily prepared headers
206 If you say 'y' here, then the path below is expected to point to a
207 tarball of such a directory.
209 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
210 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
212 Now, passing a tarball around is easier than passing a directory, so
213 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
214 say 'y' here, and enter the path to this tarball below.
216 config KERNEL_LINUX_CUSTOM_PATH
218 prompt "Path to custom headers directory/tarball"
220 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
222 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS