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_36
33 config KERNEL_V_2_6_35_8
37 config KERNEL_V_2_6_34_7
41 config KERNEL_V_2_6_33_7
45 config KERNEL_V_2_6_32_25
47 prompt "2.6.32.25 (long-term stable)"
49 The Linux 2.6.32 tree is the current "long-term stable" maintenance branch.
50 It is intended to fill the niche for users who are not using distribution
51 kernels but want to use a regression-free kernel for a longer time.
53 Critical bug fixes to later 2.6 releases are often ported to this branch
54 which makes 2.6.32 a very useful base for many embedded developers seeking
55 stable APIs or those who do not need the latest bleeding edge features.
57 ... and no, this kernel has not undergone any specific QA testing.
59 See the original announcement by Greg Kroah-Hartman in the following
61 http://marc.info/?l=linux-kernel&m=126384198403392&w=2
63 config KERNEL_V_2_6_31_14
67 config KERNEL_V_2_6_27_55
69 prompt "2.6.27.55 (old long-term stable)"
71 The Linux 2.6.27 tree is the previous "long-term stable" maintenance branch.
72 It is intended to fill the niche for users who are not using distribution
73 kernels but want to use a regression-free kernel for a longer time.
75 Critical bug fixes to later 2.6 releases are often ported to this branch
76 which makes 2.6.27 a very useful base for many embedded developers seeking
77 stable APIs or those who do not need the latest bleeding edge features.
79 ... and no, this kernel has not undergone any specific QA testing.
81 See the original announcement by Adrian Bunk in the following mailing list
83 http://marc.info/?l=linux-kernel&m=122375909403298&w=2
85 config KERNEL_LINUX_CUSTOM
87 prompt "custom tarball"
89 Use a local tarball of a complete kernel source tree.
91 config KERNEL_LINUX_CUSTOM_TARBALL
93 prompt "Path to custom tarball"
94 depends on KERNEL_LINUX_CUSTOM
96 Enter here the path to the tarball of your full kernel tree.
100 config KERNEL_VERSION
102 # Don't remove next line
103 # CT_INSERT_VERSION_STRING_BELOW
104 default "2.6.36" if KERNEL_V_2_6_36
105 default "2.6.35.8" if KERNEL_V_2_6_35_8
106 default "2.6.34.7" if KERNEL_V_2_6_34_7
107 default "2.6.33.7" if KERNEL_V_2_6_33_7
108 default "2.6.32.25" if KERNEL_V_2_6_32_25
109 default "2.6.31.14" if KERNEL_V_2_6_31_14
110 default "2.6.27.55" if KERNEL_V_2_6_27_55
114 prompt "Kernel verbosity:"
115 default KERNEL_LINUX_VERBOSITY_0
117 config KERNEL_LINUX_VERBOSITY_0
121 Print simplified command lines.
123 config KERNEL_LINUX_VERBOSITY_1
125 prompt "Full commands"
127 Print full command lines.
129 config KERNEL_LINUX_VERBOSITY_2
131 prompt "Exec reasons"
133 Print the reasons why a make target is rebuild.
137 config KERNEL_LINUX_VERBOSE_LEVEL
139 default 0 if KERNEL_LINUX_VERBOSITY_0
140 default 1 if KERNEL_LINUX_VERBOSITY_1
141 default 2 if KERNEL_LINUX_VERBOSITY_2
143 config KERNEL_LINUX_INSTALL_CHECK
145 prompt "Check installed headers"
148 If you are in doubt that installed headers are buggy, say 'Y'
149 here to have an extra check passed onto the headers.
151 endif # KERNEL_LINUX_INSTALL
153 config KERNEL_LINUX_USE_CUSTOM_HEADERS
155 prompt "pre-installed headers tree"
157 If you have some pre-installed kernel headers lying around, you can
158 enter the path to these headers, below, they will be copied from
159 there, and into the toolchain's sysroot.
162 This will *not* let you use a complete kernel tree!
163 If you want to use your own full kernel tree, then you want to
164 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
166 if KERNEL_LINUX_USE_CUSTOM_HEADERS
168 config KERNEL_LINUX_CUSTOM_IS_TARBALL
170 prompt "This is a tarball"
173 If you say 'n' here, the path below is expected to point to a directory
174 containing readily prepared headers
176 If you say 'y' here, then the path below is expected to point to a
177 tarball of such a directory.
179 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
180 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
182 Now, passing a tarball around is easier than passing a directory, so
183 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
184 say 'y' here, and enter the path to this tarball below.
186 config KERNEL_LINUX_CUSTOM_PATH
188 prompt "Path to custom headers directory/tarball"
190 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
192 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS