config/debug/gdb.in.gdbserver
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 1844 4d6a56579d9d
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>
     1 # Menu for the native gdbserver
     2 
     3 config GDB_GDBSERVER
     4     bool
     5     prompt "gdbserver"
     6     default n
     7     depends on ! BARE_METAL
     8     help
     9       Build and install a gdbserver for the target, to run on the target.
    10 
    11 if GDB_GDBSERVER
    12 
    13 config GDB_GDBSERVER_STATIC
    14     bool
    15     prompt "Build a static gdbserver"
    16     default y
    17     help
    18       In case you have trouble with dynamic loading of shared libraries,
    19       you will find that a static gdbserver comes in handy.
    20 
    21 endif # GDB_GDBSERVER
    22 
    23 if BARE_METAL
    24 comment "In bare-metal, you'll need to   "
    25 comment "provide your own gdbserver stub."
    26 endif # BARE_METAL