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>

# Dummy config file to not use a C library *at all*

# depends on BARE_METAL

config LIBC_none

    help

      Do not use a C library.

      This is usefull if your project is self-contained, does not rely on

      an external C library, and provides all the necessary bits.

      Most probably usefull to bootloaders, as they generally don't depend

      on the C library.

      If unsure: do *not* choose that, and use another option in the choice.