cc/gcc: allow CC_EXTRA_CONFIG_ARRAY on baremetal

The final bare-metal compiler is built using the core backend.
Currently the core uses the CC_CORE_EXTRA_CONFIG_ARRAY variable.

While this works as supposed to, this can leave the user puzzled
in the menuconfig, since all he can see is the core options, not
the final options.

Only show the core options if any of the core passes are needed,
and use the final options in the core-backend if we're issuing
the bare-metal compiler.

Signed-off-by: Cody P Schafer <dev@codyps.com>
[yann.morin.1998@free.fr: hide core options if no core pass needed;
use final option in core backend if issuing the bare-metal compiler]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <22181e546ba746202489.1399688067@localhost>
Patchwork-Id: 347586

#!@@CT_bash@@

# What we need:

#  - the .config file

# Parse the tools' paths configuration

. "${CT_LIB_DIR}/paths.sh"

# We'll need the stdout later, save it

exec 9>&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.2

# 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}" >&9