|author||Thomas Petazzoni <email@example.com>||2012-03-14 23:49:57 +0100|
|committer||Peter Korsgaard <firstname.lastname@example.org>||2012-03-15 23:04:39 +0100|
debug: provide an option to copy the gdbserver to the target
When an external toolchain is used, it is very likely that it contains a pre-built version of a gdbserver that has the same version as the cross-gdb included in the external toolchain. So, we now provide an option that allows to copy this pre-built gdbserver to the target. As the location of the gdbserver in the external toolchain is not standardized, we only support the CodeSourcery and Crosstool-NG layouts for the moment. Other locations can be added later. Signed-off-by: Thomas Petazzoni <email@example.com> Signed-off-by: Peter Korsgaard <firstname.lastname@example.org>
Diffstat (limited to 'toolchain/gdb')
1 files changed, 8 insertions, 0 deletions
diff --git a/toolchain/gdb/Config.in b/toolchain/gdb/Config.in
index 8501983aa4..980666b0d5 100644
@@ -14,10 +14,18 @@ comment "Gdb debugger for the target needs WCHAR support in toolchain"
bool "Build gdb server for the Target"
+ depends on !BR2_TOOLCHAIN_EXTERNAL
Build the gdbserver stub to run on the target.
A full gdb is needed to debug the progam.
+ bool "Copy gdb server to the Target"
+ depends on BR2_TOOLCHAIN_EXTERNAL
+ Copy the gdbserver provided by the external toolchain to the
bool "Build gdb for the Host"
# cross-gdb is supposed to be part of the external