config/debug/gdb.in.cross
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Jan 28 22:06:49 2011 +0100 (2011-01-28)
changeset 2284 7ede374110e5
parent 2098 9a8f0e3fe605
child 2484 d1a8c2ae7946
permissions -rw-r--r--
config: add an option not to remove the destination directory

In certain circumstances, removing the destination/installation directory
is a bad idea. For example, when the build environment is already taking
care of sanitising the build tree, and pre-installs stuff in there, it is
a very bad idea to remove the destination directory.

This happens now in buildroot, as the crostool-NG backend now installs the
toolchain in the common host-tools directory, and pre-install there a few
host-utilities (eg. host-automake and host-gawk).

Provide a config knob to turn on/off the removal of the destination
directory, defaulting to 'y' (previous behavior), and forced to 'n' when
used as a backend.

Reported-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 # Menu for the cross GDB
     2 
     3 config STATIC_TOOLCHAIN
     4     select GDB_CROSS_STATIC if GDB_CROSS
     5 
     6 config GDB_CROSS
     7     bool
     8     prompt "Cross-gdb"
     9     default y
    10     select GDB_GDBSERVER if ! BARE_METAL
    11     help
    12       Build and install a cross-gdb for the target, to run on host.
    13 
    14 if GDB_CROSS
    15 
    16 config GDB_CROSS_STATIC
    17     bool
    18     prompt "Build a static cross gdb"
    19     default n
    20     help
    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.
    23       
    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.
    26 
    27 endif # GDB_CROSS