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_33_7
41 config KERNEL_V_2_6_32_17
45 config KERNEL_V_2_6_31_14
49 config KERNEL_V_2_6_27_49
51 prompt "2.6.27.49 (long-term stable)"
53 The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
54 It is intended to fill the niche for users who are not using distribution
55 kernels but want to use a regression-free kernel for a longer time.
57 Critical bug fixes to later 2.6 releases are often ported to this branch
58 which makes 2.6.27 a very useful base for many embedded developers seeking
59 stable APIs or those who do not need the latest bleeding edge features.
61 ... and no, this kernel has not undergone any specific QA testing.
63 See the original announcement by Adrian Bunk in the following mailing list
64 entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
66 config KERNEL_LINUX_CUSTOM
68 prompt "custom tarball"
70 Use a local tarball of a complete kernel source tree.
72 config KERNEL_LINUX_CUSTOM_TARBALL
74 prompt "Path to custom tarball"
75 depends on KERNEL_LINUX_CUSTOM
77 Enter here the path to the tarball of your full kernel tree.
83 # Don't remove next line
84 # CT_INSERT_VERSION_STRING_BELOW
85 default "2.6.35" if KERNEL_V_2_6_35
86 default "2.6.34.2" if KERNEL_V_2_6_34_2
87 default "2.6.33.7" if KERNEL_V_2_6_33_7
88 default "2.6.32.17" if KERNEL_V_2_6_32_17
89 default "2.6.31.14" if KERNEL_V_2_6_31_14
90 default "2.6.27.49" if KERNEL_V_2_6_27_49
94 prompt "Kernel verbosity:"
95 default KERNEL_LINUX_VERBOSITY_0
97 config KERNEL_LINUX_VERBOSITY_0
101 Print simplified command lines.
103 config KERNEL_LINUX_VERBOSITY_1
105 prompt "Full commands"
107 Print full command lines.
109 config KERNEL_LINUX_VERBOSITY_2
111 prompt "Exec reasons"
113 Print the reasons why a make target is rebuild.
117 config KERNEL_LINUX_VERBOSE_LEVEL
119 default 0 if KERNEL_LINUX_VERBOSITY_0
120 default 1 if KERNEL_LINUX_VERBOSITY_1
121 default 2 if KERNEL_LINUX_VERBOSITY_2
123 config KERNEL_LINUX_INSTALL_CHECK
125 prompt "Check installed headers"
128 If you are in doubt that installed headers are buggy, say 'Y'
129 here to have an extra check passed onto the headers.
131 endif # KERNEL_LINUX_INSTALL
133 config KERNEL_LINUX_USE_CUSTOM_HEADERS
135 prompt "pre-installed headers tree"
137 If you have some pre-installed kernel headers lying around, you can
138 enter the path to these headers, below, they will be copied from
139 there, and into the toolchain's sysroot.
142 This will *not* let you use a complete kernel tree!
143 If you want to use your own full kernel tree, then you want to
144 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
146 if KERNEL_LINUX_USE_CUSTOM_HEADERS
148 config KERNEL_LINUX_CUSTOM_IS_TARBALL
150 prompt "This is a tarball"
153 If you say 'n' here, the path below is expected to point to a directory
154 containing readily prepared headers
156 If you say 'y' here, then the path below is expected to point to a
157 tarball of such a directory.
159 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
160 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
162 Now, passing a tarball around is easier than passing a directory, so
163 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
164 say 'y' here, and enter the path to this tarball below.
166 config KERNEL_LINUX_CUSTOM_PATH
168 prompt "Path to custom headers directory/tarball"
170 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
172 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS