config/debug/gdb.in.native
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 1850 136a929ec37f
child 2484 d1a8c2ae7946
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     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_NO_STATIC
    15     bool
    16     default n
    17 
    18 config GDB_NATIVE_STATIC
    19     bool
    20     prompt "Build a static native gdb"
    21     depends on ! GDB_NATIVE_NO_STATIC
    22     default n
    23     help
    24       In case you have trouble with dynamic loading of shared libraries,
    25       you will find that a static gdb comes in handy.
    26 
    27 endif # GDB_NATIVE