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>

#!@@CT_bash@@

# What we need:

#  - the .config file

# Parse the tools' paths configuration

. "${CT_LIB_DIR}/paths.mk"

# We'll need the stdout later, save it

exec 7>&1

# Parse the common functions

. "${CT_LIB_DIR}/scripts/functions"

# Don't care about any log file

exec >/dev/null

rm -f "${tmp_log_file}"

# Parse the configuration file

. .config

# Parse architecture and kernel specific functions

. "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"

. "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"

# Build CT_TARGET

CT_DoBuildTargetTuple

# All this for this single echo... :-( Sigh, I'll have to re-arrange things...

echo "${CT_TARGET}" >&7