config/debug/gdb.in.gdbserver
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307 2efd46963086
parent 1844 4d6a56579d9d
child 2484 d1a8c2ae7946
permissions -rw-r--r--
buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@1849
     1
# Menu for the native gdbserver
yann@622
     2
yann@583
     3
config GDB_GDBSERVER
yann@583
     4
    bool
yann@583
     5
    prompt "gdbserver"
yann@583
     6
    default n
yann@850
     7
    depends on ! BARE_METAL
yann@583
     8
    help
yann@583
     9
      Build and install a gdbserver for the target, to run on the target.
yann@583
    10
yann@1849
    11
if GDB_GDBSERVER
yann@1849
    12
yann@583
    13
config GDB_GDBSERVER_STATIC
yann@175
    14
    bool
yann@175
    15
    prompt "Build a static gdbserver"
yann@622
    16
    default y
yann@175
    17
    help
yann@175
    18
      In case you have trouble with dynamic loading of shared libraries,
yann@175
    19
      you will find that a static gdbserver comes in handy.
yann@175
    20
yann@1849
    21
endif # GDB_GDBSERVER
yann@1849
    22
yann@1269
    23
if BARE_METAL
yann@1269
    24
comment "In bare-metal, you'll need to   "
yann@1269
    25
comment "provide your own gdbserver stub."
yann@1269
    26
endif # BARE_METAL