1 # Menu for the cross GDB
3 config STATIC_TOOLCHAIN
4 select GDB_CROSS_STATIC if GDB_CROSS
6 comment "Cross-gdb - disabled (requires expat; re-run ./configure to enable)"
7 depends on !CONFIGURE_has_expat
9 comment "Static cross-gdb - disabled (requires static expat; re-run ./configure to enable)"
10 depends on STATIC_TOOLCHAIN && !CONFIGURE_has_static_expat
16 depends on CONFIGURE_has_expat
17 depends on !STATIC_TOOLCHAIN || CONFIGURE_has_static_expat
18 select GDB_GDBSERVER if ! BARE_METAL
20 Build and install a cross-gdb for the target, to run on host.
24 config GDB_CROSS_STATIC
26 prompt "Build a static cross gdb"
27 depends on CONFIGURE_static_link_ok
28 depends on CONFIGURE_has_static_expat
30 A static cross gdb can be usefull if you debug on a machine that is
31 not the one that is used to compile the toolchain.
33 That way, you can share the cross-gdb without installing a toolchain
34 on every machine that will be used to debug target programs.
36 config GDB_CROSS_PYTHON
38 prompt "Enable python scripting"
39 depends on CONFIGURE_has_python
40 depends on ! GDB_CROSS_STATIC
43 Say 'y' if you want to use Python scripting inside gdb.
44 Say 'n' if you do not want to.
46 Beware that enabling Python scripting could render the gdb
47 executable non-functional if you move it to another machine.
48 Building a static gdb can help in this regard, although there
49 have been reports of problems when linking gdb to the static
50 libpython.a. This should be fixed in gdb >=7.3. YMMV.