diff options
| -rw-r--r-- | config/debug/gdb.in.cross | 16 | ||||
| -rwxr-xr-x | configure | 1 | ||||
| -rw-r--r-- | scripts/build/debug/300-gdb.sh | 5 |
3 files changed, 22 insertions, 0 deletions
diff --git a/config/debug/gdb.in.cross b/config/debug/gdb.in.cross index cbe8b297..633def38 100644 --- a/config/debug/gdb.in.cross +++ b/config/debug/gdb.in.cross @@ -33,4 +33,20 @@ config GDB_CROSS_STATIC 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 @@ -609,6 +609,7 @@ done has_or_warn inc="${python_incs}" \ lib="${python_libs}" \ lib_exts="${libs_exts}" \ + kconfig=has_python \ err="The 'python' header file and library are needed for some features of cross-gdb" #--------------------------------------------------------------------- diff --git a/scripts/build/debug/300-gdb.sh b/scripts/build/debug/300-gdb.sh index 99356d76..289d26a9 100644 --- a/scripts/build/debug/300-gdb.sh +++ b/scripts/build/debug/300-gdb.sh @@ -118,6 +118,11 @@ do_debug_gdb_build() { none) cross_extra_config+=("--disable-threads");; *) cross_extra_config+=("--enable-threads");; esac + if [ "${CT_GDB_CROSS_PYTHON}" = "y" ]; then + cross_extra_config+=( "--with-python=yes" ) + else + cross_extra_config+=( "--with-python=no" ) + fi CC_for_gdb= LD_for_gdb= |