config/debug/gdb.in.native
author Bart vdr. Meulen <bartvdrmeulen@gmail.com>
Mon Jul 19 23:16:02 2010 +0200 (2010-07-19)
branch1.7
changeset 2046 471acb219d77
parent 1849 73f76483a389
child 2098 9a8f0e3fe605
permissions -rw-r--r--
complibs: fix using static companion libraries

When building a cross-compiler for a target which uses a file extension for
binaries the symbolic link to cc is not created correctly because the lookup
of the gcc binary is done in a incorrect path

Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
(transplanted from 3917f2dafed1bb189e39f50e8506b3141926d7e1)
     1 # Menu for the native GDB
     2 
     3 config GDB_NATIVE
     4     bool
     5     prompt "Native gdb"
     6     default n
     7     depends on ! BARE_METAL
     8     depends on ! BACKEND
     9     help
    10       Build and install a native gdb for the target, to run on the target.
    11 
    12 if GDB_NATIVE
    13 
    14 config GDB_NATIVE_USE_GMP_MPFR
    15     bool
    16     prompt "Use GMP and MPFR"
    17     default n
    18     select GMP_TARGET
    19     select MPFR_TARGET
    20     select GDB_NATIVE_NO_STATIC
    21     help
    22       gdb can make use of the GMP and MPFR libraries.
    23       
    24       While the cross-gdb (above) can use the libraries compiled for the
    25       host, the native gdb needs the libraries for the target (where it will
    26       eventually run).
    27       
    28       Setting this option will force building the GMP and MPFR libraries for
    29       the target, and configure the native gdb to use them.
    30 
    31 config GDB_NATIVE_NO_STATIC
    32     bool
    33     default n
    34 
    35 config GDB_NATIVE_STATIC
    36     bool
    37     prompt "Build a static native gdb"
    38     depends on ! GDB_NATIVE_NO_STATIC
    39     default n
    40     help
    41       In case you have trouble with dynamic loading of shared libraries,
    42       you will find that a static gdb comes in handy.
    43 
    44 endif # GDB_NATIVE