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_34
33 config KERNEL_V_2_6_33_5
37 config KERNEL_V_2_6_33_4
41 config KERNEL_V_2_6_33_3
45 config KERNEL_V_2_6_33_2
49 config KERNEL_V_2_6_33_1
53 config KERNEL_V_2_6_33
57 config KERNEL_V_2_6_32_14
61 config KERNEL_V_2_6_31_13
65 config KERNEL_V_2_6_30_10
69 config KERNEL_V_2_6_27_47
71 prompt "2.6.27.47 (long-term stable)"
73 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
74 It is intended to fill the niche for users who are not using distribution
75 kernels but want to use a regression-free kernel for a longer time.
77 Critical bug fixes to later 2.6 releases are often ported to this branch
78 which makes 2.6.27 a very useful base for many embedded developers seeking
79 stable APIs or those who do not need the latest bleeding edge features.
81 ... and no, this kernel has not undergone any specific QA testing.
83 See the original announcement by Adrian Bunk in the following mailing list
84 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
86 config KERNEL_LINUX_CUSTOM
88 prompt "custom tarball"
90 Use a local tarball of a complete kernel source tree.
92 config KERNEL_LINUX_CUSTOM_TARBALL
94 prompt "Path to custom tarball"
95 depends on KERNEL_LINUX_CUSTOM
97 Enter here the path to the tarball of your full kernel tree.
101 config KERNEL_VERSION
103 # Don't remove next line
104 # CT_INSERT_VERSION_STRING_BELOW
105 default "2.6.34" if KERNEL_V_2_6_34
106 default "2.6.33.5" if KERNEL_V_2_6_33_5
107 default "2.6.33.4" if KERNEL_V_2_6_33_4
108 default "2.6.33.3" if KERNEL_V_2_6_33_3
109 default "2.6.33.2" if KERNEL_V_2_6_33_2
110 default "2.6.33.1" if KERNEL_V_2_6_33_1
111 default "2.6.33" if KERNEL_V_2_6_33
112 default "2.6.32.14" if KERNEL_V_2_6_32_14
113 default "2.6.31.13" if KERNEL_V_2_6_31_13
114 default "2.6.30.10" if KERNEL_V_2_6_30_10
115 default "2.6.27.47" if KERNEL_V_2_6_27_47
119 prompt "Kernel verbosity:"
120 default KERNEL_LINUX_VERBOSITY_0
122 config KERNEL_LINUX_VERBOSITY_0
126 Print simplified command lines.
128 config KERNEL_LINUX_VERBOSITY_1
130 prompt "Full commands"
132 Print full command lines.
134 config KERNEL_LINUX_VERBOSITY_2
136 prompt "Exec reasons"
138 Print the reasons why a make target is rebuild.
142 config KERNEL_LINUX_VERBOSE_LEVEL
144 default 0 if KERNEL_LINUX_VERBOSITY_0
145 default 1 if KERNEL_LINUX_VERBOSITY_1
146 default 2 if KERNEL_LINUX_VERBOSITY_2
148 config KERNEL_LINUX_INSTALL_CHECK
150 prompt "Check installed headers"
153 If you are in doubt that installed headers are buggy, say 'Y'
154 here to have an extra check passed onto the headers.
156 endif # KERNEL_LINUX_INSTALL
158 config KERNEL_LINUX_USE_CUSTOM_HEADERS
160 prompt "pre-installed headers tree"
162 If you have some pre-installed kernel headers lying around, you can
163 enter the path to these headers, below, they will be copied from
164 there, and into the toolchain's sysroot.
167 This will *not* let you use a complete kernel tree!
168 If you want to use your own full kernel tree, then you want to
169 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
171 if KERNEL_LINUX_USE_CUSTOM_HEADERS
173 config KERNEL_LINUX_CUSTOM_IS_TARBALL
175 prompt "This is a tarball"
178 If you say 'n' here, the path below is expected to point to a directory
179 containing readily prepared headers
181 If you say 'y' here, then the path below is expected to point to a
182 tarball of such a directory.
184 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
185 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
187 Now, passing a tarball around is easier than passing a directory, so
188 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
189 say 'y' here, and enter the path to this tarball below.
191 config KERNEL_LINUX_CUSTOM_PATH
193 prompt "Path to custom headers directory/tarball"
195 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
197 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS