blob: e89cdf6345b2b56d728788e92aba64ce0711c908 (
plain)
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
|
#
config NATIVE_TOOLCHAIN
bool
prompt "Use host's toolchain" if DEVEL && BROKEN
default n
help
If enabled, OpenWrt will compile using your existing toolchain instead of compiling one
menuconfig TOOLCHAINOPTS
bool "Toolchain Options" if DEVEL
depends !NATIVE_TOOLCHAIN
source "toolchain/binutils/Config.in"
source "toolchain/gcc/Config.in"
config GDB
bool
prompt "Build gdb" if TOOLCHAINOPTS
default n
help
Enable if you want to build the gdb
config LARGEFILE
bool
prompt "Enable large file (files > 2 GB) support?" if TOOLCHAINOPTS
depends on !cris
default y
help
Enable large file (files > 2 GB) support
config C99_MATH
bool
prompt "Enable full C99 math support?" if TOOLCHAINOPTS
default n
help
Enable if you need full C99 math in libm
config SOFT_FLOAT
bool
prompt "Use software floating point by default" if TOOLCHAINOPTS
default n
depends on arm || mips || powerpc
help
If your target CPU does not have a Floating Point Unit (FPU) or a
kernel FPU emulator, but you still wish to support floating point
functions, then everything will need to be compiled with soft floating
point support (-msoft-float).
Most people will answer N.
config TARGET_OPTIMIZATION
string
prompt "Target Optimizations" if TOOLCHAINOPTS
default "-Os -pipe -march=i486 -funit-at-a-time" if i386
default "-Os -pipe -mips32 -mtune=mips32 -funit-at-a-time" if mipsel || mips
default "-Os -pipe -mcpu=xscale -funit-at-a-time" if armeb
default "-Os -pipe -funit-at-a-time"
help
Optimizations to use when building for the target host.
source "toolchain/gcc/Config.version"
|
