crosstool-ng: config/debug/gdb.in.gdbserver@730e2d63296b

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 gdbserver

     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.

    11 if GDB_GDBSERVER

    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.

    21 endif # GDB_GDBSERVER

    23 if BARE_METAL

    24 comment "In bare-metal, you'll need to   "

    25 comment "provide your own gdbserver stub."

    26 endif # BARE_METAL

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 1844	4d6a56579d9d
child 2484	d1a8c2ae7946
permissions	-rw-r--r--