config/debug/gdb.in.native
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Sun May 11 13:38:12 2014 +0200 (2014-05-11)
changeset 3313 ad14212ebf54
parent 2484 d1a8c2ae7946
permissions -rw-r--r--
config: switch cc with libc in the config order

Some of the compiler options depend on the C library choice, (e.g.
whether core passes are needed).

Since the compiler menu comes before the C library menu, those options
may or may not be visible until the C library is chosen, leading to
either options being visible by the user (thus be puzzling as they would
not apply to his case), or invisible to him (yet again puzzling him).

Invert the order of the compiler and the C library in the menuconfig. It
anyway looks more rational, in the end.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
     1 # Menu for the native GDB
     2 
     3 config GDB_NATIVE
     4     bool
     5     prompt "Native gdb"
     6     depends on ! BARE_METAL
     7     depends on ! BACKEND
     8     help
     9       Build and install a native gdb for the target, to run on the target.
    10 
    11 if GDB_NATIVE
    12 
    13 config GDB_NATIVE_STATIC
    14     bool
    15     prompt "Build a static native gdb"
    16     help
    17       In case you have trouble with dynamic loading of shared libraries,
    18       you will find that a static gdb comes in handy.
    19 
    20 endif # GDB_NATIVE