config/debug/gdb.in.cross
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 2098 9a8f0e3fe605
child 2484 d1a8c2ae7946
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@1849
     1
# Menu for the cross GDB
yann@96
     2
yann@2209
     3
config STATIC_TOOLCHAIN
yann@2209
     4
    select GDB_CROSS_STATIC if GDB_CROSS
yann@2209
     5
yann@96
     6
config GDB_CROSS
yann@96
     7
    bool
yann@96
     8
    prompt "Cross-gdb"
yann@96
     9
    default y
yann@850
    10
    select GDB_GDBSERVER if ! BARE_METAL
yann@96
    11
    help
yann@583
    12
      Build and install a cross-gdb for the target, to run on host.
yann@96
    13
yann@1849
    14
if GDB_CROSS
yann@1849
    15
yann@1915
    16
config GDB_CROSS_STATIC
yann@1915
    17
    bool
yann@1915
    18
    prompt "Build a static cross gdb"
yann@1915
    19
    default n
yann@1915
    20
    help
yann@1915
    21
      A static cross gdb can be usefull if you debug on a machine that is
yann@1915
    22
      not the one that is used to compile the toolchain.
yann@1915
    23
      
yann@1915
    24
      That way, you can share the cross-gdb without installing a toolchain
yann@1915
    25
      on every machine that will be used to debug target programs.
yann@1915
    26
yann@1849
    27
endif # GDB_CROSS