config/debug/gdb.in.native
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 1850 136a929ec37f
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 GDB
yann@821
     2
yann@583
     3
config GDB_NATIVE
yann@583
     4
    bool
yann@583
     5
    prompt "Native gdb"
yann@583
     6
    default n
yann@850
     7
    depends on ! BARE_METAL
yann@1844
     8
    depends on ! BACKEND
yann@583
     9
    help
yann@583
    10
      Build and install a native gdb for the target, to run on the target.
yann@583
    11
yann@1849
    12
if GDB_NATIVE
yann@1849
    13
yann@1850
    14
config GDB_NATIVE_NO_STATIC
yann@1850
    15
    bool
yann@1850
    16
    default n
yann@1850
    17
yann@1850
    18
config GDB_NATIVE_STATIC
yann@1850
    19
    bool
yann@1850
    20
    prompt "Build a static native gdb"
yann@1850
    21
    depends on ! GDB_NATIVE_NO_STATIC
yann@1850
    22
    default n
yann@1850
    23
    help
yann@1850
    24
      In case you have trouble with dynamic loading of shared libraries,
yann@1850
    25
      you will find that a static gdb comes in handy.
yann@1850
    26
yann@1849
    27
endif # GDB_NATIVE