2010-03-15 20:42:55 +00:00
|
|
|
# Menu for the cross GDB
|
|
|
|
|
2010-12-09 17:55:15 +00:00
|
|
|
config STATIC_TOOLCHAIN
|
|
|
|
select GDB_CROSS_STATIC if GDB_CROSS
|
|
|
|
|
debug/cross-gdb: check host dependencies
Cross-gdb depends on expat and python. If either is missing, cross-gdb will
build successfully, but lacking some features.
Especially, if expat is missing, cross-gdb will be unable to parse the target
description, which may lead to runtime malfunctions and the following GDB
warning:
"Can not parse XML target description; XML support was disabled at compile time"
Hence, expat should be considered mandatory.
On the other hand, the features missing without python are not critical, so
python should not be considered mandatory.
This patch does the following:
- At configure time, warn the user if either expat or python is missing.
- In menuconfig, disable the static build options regarding cross-gdb if no
static version of expat is available, and disable cross-gdb if expat is
missing.
Signed-off-by: "Benoît THÉBAUDEAU" <benoit.thebaudeau@advansee.com>
[yann.morin.1998@anciens.enib.fr: add comment for impossible static cross-gdb]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-06-08 13:47:43 +00:00
|
|
|
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
|
|
|
|
|
2010-03-15 20:42:55 +00:00
|
|
|
config GDB_CROSS
|
|
|
|
bool
|
|
|
|
prompt "Cross-gdb"
|
|
|
|
default y
|
debug/cross-gdb: check host dependencies
Cross-gdb depends on expat and python. If either is missing, cross-gdb will
build successfully, but lacking some features.
Especially, if expat is missing, cross-gdb will be unable to parse the target
description, which may lead to runtime malfunctions and the following GDB
warning:
"Can not parse XML target description; XML support was disabled at compile time"
Hence, expat should be considered mandatory.
On the other hand, the features missing without python are not critical, so
python should not be considered mandatory.
This patch does the following:
- At configure time, warn the user if either expat or python is missing.
- In menuconfig, disable the static build options regarding cross-gdb if no
static version of expat is available, and disable cross-gdb if expat is
missing.
Signed-off-by: "Benoît THÉBAUDEAU" <benoit.thebaudeau@advansee.com>
[yann.morin.1998@anciens.enib.fr: add comment for impossible static cross-gdb]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-06-08 13:47:43 +00:00
|
|
|
depends on CONFIGURE_has_expat
|
|
|
|
depends on !STATIC_TOOLCHAIN || CONFIGURE_has_static_expat
|
2010-03-15 20:42:55 +00:00
|
|
|
select GDB_GDBSERVER if ! BARE_METAL
|
|
|
|
help
|
|
|
|
Build and install a cross-gdb for the target, to run on host.
|
|
|
|
|
|
|
|
if GDB_CROSS
|
|
|
|
|
2010-04-15 17:54:00 +00:00
|
|
|
config GDB_CROSS_STATIC
|
|
|
|
bool
|
|
|
|
prompt "Build a static cross gdb"
|
debug/cross-gdb: check host dependencies
Cross-gdb depends on expat and python. If either is missing, cross-gdb will
build successfully, but lacking some features.
Especially, if expat is missing, cross-gdb will be unable to parse the target
description, which may lead to runtime malfunctions and the following GDB
warning:
"Can not parse XML target description; XML support was disabled at compile time"
Hence, expat should be considered mandatory.
On the other hand, the features missing without python are not critical, so
python should not be considered mandatory.
This patch does the following:
- At configure time, warn the user if either expat or python is missing.
- In menuconfig, disable the static build options regarding cross-gdb if no
static version of expat is available, and disable cross-gdb if expat is
missing.
Signed-off-by: "Benoît THÉBAUDEAU" <benoit.thebaudeau@advansee.com>
[yann.morin.1998@anciens.enib.fr: add comment for impossible static cross-gdb]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-06-08 13:47:43 +00:00
|
|
|
depends on CONFIGURE_has_static_expat
|
2010-04-15 17:54:00 +00:00
|
|
|
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.
|
|
|
|
|
2010-03-15 20:42:55 +00:00
|
|
|
endif # GDB_CROSS
|