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_32_17
53 config KERNEL_V_2_6_31_14
57 config KERNEL_V_2_6_30_10
61 config KERNEL_V_2_6_27_49
63 prompt "2.6.27.49 (long-term stable)"
65 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
66 It is intended to fill the niche for users who are not using distribution
67 kernels but want to use a regression-free kernel for a longer time.
69 Critical bug fixes to later 2.6 releases are often ported to this branch
70 which makes 2.6.27 a very useful base for many embedded developers seeking
71 stable APIs or those who do not need the latest bleeding edge features.
73 ... and no, this kernel has not undergone any specific QA testing.
75 See the original announcement by Adrian Bunk in the following mailing list
76 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
78 config KERNEL_LINUX_CUSTOM
80 prompt "custom tarball"
82 Use a local tarball of a complete kernel source tree.
84 config KERNEL_LINUX_CUSTOM_TARBALL
86 prompt "Path to custom tarball"
87 depends on KERNEL_LINUX_CUSTOM
89 Enter here the path to the tarball of your full kernel tree.
95 # Don't remove next line
96 # CT_INSERT_VERSION_STRING_BELOW
97 default "2.6.35" if KERNEL_V_2_6_35
98 default "2.6.34.2" if KERNEL_V_2_6_34_2
99 default "2.6.34.1" if KERNEL_V_2_6_34_1
100 default "2.6.34" if KERNEL_V_2_6_34
101 default "2.6.33.7" if KERNEL_V_2_6_33_7
102 default "2.6.32.17" if KERNEL_V_2_6_32_17
103 default "2.6.31.14" if KERNEL_V_2_6_31_14
104 default "2.6.30.10" if KERNEL_V_2_6_30_10
105 default "2.6.27.49" if KERNEL_V_2_6_27_49
109 prompt "Kernel verbosity:"
110 default KERNEL_LINUX_VERBOSITY_0
112 config KERNEL_LINUX_VERBOSITY_0
116 Print simplified command lines.
118 config KERNEL_LINUX_VERBOSITY_1
120 prompt "Full commands"
122 Print full command lines.
124 config KERNEL_LINUX_VERBOSITY_2
126 prompt "Exec reasons"
128 Print the reasons why a make target is rebuild.
132 config KERNEL_LINUX_VERBOSE_LEVEL
134 default 0 if KERNEL_LINUX_VERBOSITY_0
135 default 1 if KERNEL_LINUX_VERBOSITY_1
136 default 2 if KERNEL_LINUX_VERBOSITY_2
138 config KERNEL_LINUX_INSTALL_CHECK
140 prompt "Check installed headers"
143 If you are in doubt that installed headers are buggy, say 'Y'
144 here to have an extra check passed onto the headers.
146 endif # KERNEL_LINUX_INSTALL
148 config KERNEL_LINUX_USE_CUSTOM_HEADERS
150 prompt "pre-installed headers tree"
152 If you have some pre-installed kernel headers lying around, you can
153 enter the path to these headers, below, they will be copied from
154 there, and into the toolchain's sysroot.
157 This will *not* let you use a complete kernel tree!
158 If you want to use your own full kernel tree, then you want to
159 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
161 if KERNEL_LINUX_USE_CUSTOM_HEADERS
163 config KERNEL_LINUX_CUSTOM_IS_TARBALL
165 prompt "This is a tarball"
168 If you say 'n' here, the path below is expected to point to a directory
169 containing readily prepared headers
171 If you say 'y' here, then the path below is expected to point to a
172 tarball of such a directory.
174 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
175 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
177 Now, passing a tarball around is easier than passing a directory, so
178 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
179 say 'y' here, and enter the path to this tarball below.
181 config KERNEL_LINUX_CUSTOM_PATH
183 prompt "Path to custom headers directory/tarball"
185 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
187 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS