1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
# Linux kernel options
## select KERNEL_SUPPORTS_SHARED_LIBS
##
## help Build a toolchain targeting systems running Linux as a kernel.
config KERNEL_LINUX_USE_CUSTOM_HEADERS
bool
prompt "Use pre-installed headers tree (OBSOLETE)"
depends on OBSOLETE
help
If you have some pre-installed kernel headers lying around, you can
enter the path to these headers, below, they will be copied from
there, and into the toolchain's sysroot.
Note:
This will *not* let you use a complete kernel tree!
If you want to use your own full kernel tree, then you want to say 'N'
here, and select KERNEL_LINUX_CUSTOM, in the versions list, below.
if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
choice
bool
prompt "Linux kernel version"
# Don't remove next line
# CT_INSERT_VERSION_BELOW
config KERNEL_V_4_0
bool
prompt "4.0.5 (stable)"
config KERNEL_V_3_19
bool
prompt "3.19.8 (EOL)"
config KERNEL_V_3_18
bool
prompt "3.18.16"
config KERNEL_V_3_14
bool
prompt "3.14.44"
config KERNEL_V_3_12
bool
prompt "3.12.44"
config KERNEL_V_3_10
bool
prompt "3.10.80"
config KERNEL_V_3_4
bool
prompt "3.4.107"
config KERNEL_V_3_2
bool
prompt "3.2.69"
config KERNEL_V_2_6_32
bool
prompt "2.6.32.67"
help
config KERNEL_LINUX_CUSTOM
bool
prompt "custom tarball or directory"
help
Use a local tarball or local kernel directory of a complete kernel source tree.
config KERNEL_LINUX_CUSTOM_LOCATION
string
prompt "Path to custom source, tarball or directory"
depends on KERNEL_LINUX_CUSTOM
help
Enter here the path to the tarball of your full kernel tree or
kernel directory
endchoice
config KERNEL_VERSION
string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
default "4.0.5" if KERNEL_V_4_0
default "3.19.8" if KERNEL_V_3_19
default "3.18.16" if KERNEL_V_3_18
default "3.14.44" if KERNEL_V_3_14
default "3.12.44" if KERNEL_V_3_12
default "3.10.80" if KERNEL_V_3_10
default "3.4.107" if KERNEL_V_3_4
default "3.2.69" if KERNEL_V_3_2
default "2.6.32.67" if KERNEL_V_2_6_32
default "custom" if KERNEL_LINUX_CUSTOM
endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
if KERNEL_LINUX_USE_CUSTOM_HEADERS
config KERNEL_LINUX_CUSTOM_PATH
string
prompt "Path to custom headers directory/tarball"
help
See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
config KERNEL_LINUX_CUSTOM_IS_TARBALL
bool
prompt "This is a tarball"
help
If you say 'n' here, the path above is expected to point to a directory
containing readily prepared headers
If you say 'y' here, then the path above is expected to point to a
tarball of such a directory.
Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
Now, passing a tarball around is easier than passing a directory, so
if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
say 'y' here, and enter the path to this tarball below.
endif # KERNEL_LINUX_USE_CUSTOM_HEADERS
|