1 # Menu for the cross GDB
3 config STATIC_TOOLCHAIN
4 select GDB_CROSS_STATIC if GDB_CROSS
10 select GDB_GDBSERVER if ! BARE_METAL
12 Build and install a cross-gdb for the target, to run on host.
16 config GDB_CROSS_STATIC
18 prompt "Build a static cross gdb"
19 select WANTS_STATIC_LINK
21 A static cross gdb can be usefull if you debug on a machine that is
22 not the one that is used to compile the toolchain.
24 That way, you can share the cross-gdb without installing a toolchain
25 on every machine that will be used to debug target programs.
30 depends on EXPERIMENTAL
32 Say 'y' here if you want to build the 'sim' emulator.
33 You probably don't want it, unless you are building for bare-metal.
36 config GDB_CROSS_PYTHON
38 prompt "Enable python scripting"
39 depends on ! GDB_CROSS_STATIC
42 Say 'y' if you want to use Python scripting inside gdb.
43 Say 'n' if you do not want to.
45 Beware that enabling Python scripting could render the gdb
46 executable non-functional if you move it to another machine.
47 Building a static gdb can help in this regard, although there
48 have been reports of problems when linking gdb to the static
49 libpython.a. This should be fixed in gdb >=7.3. YMMV.
51 config GDB_CROSS_EXTRA_CONFIG_ARRAY
53 prompt "Cross-gdb extra config"
56 Extra flags to pass onto ./configure when configuring the gdb cross.