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>

# Menu for the native GDB

config GDB_NATIVE

    bool

    prompt "Native gdb"

    default n

    depends on ! BARE_METAL

    depends on ! BACKEND

    help

      Build and install a native gdb for the target, to run on the target.

if GDB_NATIVE

config GDB_NATIVE_NO_STATIC

    bool

    default n

config GDB_NATIVE_STATIC

    bool

    prompt "Build a static native gdb"

    depends on ! GDB_NATIVE_NO_STATIC

    default n

    help

      In case you have trouble with dynamic loading of shared libraries,

      you will find that a static gdb comes in handy.

endif # GDB_NATIVE