Push the calculation of the tuple's kernel part down to kernel's build scripts:
- update the kernel script's API with the function CT_DiKernelTupleValues
- update doc accordingly (also with the architecture change, missing in the previous commit)
- small clean-up in the main script, remove useless test

/trunk/scripts/build/kernel/bare-metal.sh | 5 5 0 0 +++++
/trunk/scripts/build/kernel/linux.sh | 5 5 0 0 +++++
/trunk/scripts/crosstool.sh | 31 13 18 0 +++++++++++++------------------
/trunk/scripts/functions | 15 8 7 0 ++++++++-------
/trunk/docs/overview.txt | 13 9 4 0 +++++++++----
5 files changed, 40 insertions(+), 29 deletions(-)

 # Compute ARM-specific values

 CT_DoArchTupleValues() {

     # The architecture part of the tuple:

     CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"

     # The system part of the tuple:

     case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in

         *glibc,y)   CT_TARGET_SYS=gnueabi;;

         uClibc,y)   CT_TARGET_SYS=uclibcgnueabi;;

         none,y)     CT_TARGET_SYS=eabi;;

     esac

     # In case we're EABI, do *not* specify any ABI!

     # which means, either we do not have an ABI specified, or we're not EABI.

     CT_TestOrAbort "Internal error: CT_ARCH_ABI should not be set for EABI build." -z "${CT_ARCH_ABI}" -o -z "${CT_ARCH_ARM_EABI}"

 }