blob: 633def384e0a69c35d79afdf53a3f4e5c7a7c75d (
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
|
# Menu for the cross GDB
config STATIC_TOOLCHAIN
select GDB_CROSS_STATIC if GDB_CROSS
comment "Cross-gdb - disabled (requires expat; re-run ./configure to enable)"
depends on !CONFIGURE_has_expat
comment "Static cross-gdb - disabled (requires static expat; re-run ./configure to enable)"
depends on STATIC_TOOLCHAIN && !CONFIGURE_has_static_expat
config GDB_CROSS
bool
prompt "Cross-gdb"
default y
depends on CONFIGURE_has_expat
depends on !STATIC_TOOLCHAIN || CONFIGURE_has_static_expat
select GDB_GDBSERVER if ! BARE_METAL
help
Build and install a cross-gdb for the target, to run on host.
if GDB_CROSS
config GDB_CROSS_STATIC
bool
prompt "Build a static cross gdb"
depends on CONFIGURE_static_link_ok
depends on CONFIGURE_has_static_expat
help
A static cross gdb can be usefull if you debug on a machine that is
not the one that is used to compile the toolchain.
That way, you can share the cross-gdb without installing a toolchain
on every machine that will be used to debug target programs.
config GDB_CROSS_PYTHON
bool
prompt "Enable python scripting"
depends on CONFIGURE_has_python
depends on ! GDB_CROSS_STATIC
default y
help
Say 'y' if you want to use Python scripting inside gdb.
Say 'n' if you do not want to.
Beware that enabling Python scripting could render the gdb
executable non-functional if you move it to another machine.
Building a static gdb can help in this regard, although there
have been reports of problems when linking gdb to the static
libpython.a. This should be fixed in gdb >=7.3. YMMV.
endif # GDB_CROSS
|
