yann@1336: #!@@CT_bash@@ yann@1336: yann@1336: # What we need: yann@1336: # - the .config file yann@1336: yann@1336: # Parse the tools' paths configuration yann@1336: . "${CT_LIB_DIR}/paths.mk" yann@1336: yann@1336: # We'll need the stdout later, save it yann@1336: exec 7>&1 yann@1336: yann@1336: # Parse the common functions yann@1336: . "${CT_LIB_DIR}/scripts/functions" yann@1336: yann@1336: # Don't care about any log file yann@1336: exec >/dev/null yann@1336: rm -f "${tmp_log_file}" yann@1336: yann@1336: # Parse the configuration file yann@1336: . .config yann@1336: yann@1336: # Parse architecture and kernel specific functions yann@1336: . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh" yann@1336: . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh" yann@1336: yann@1336: # Build CT_TARGET yann@1336: CT_DoBuildTargetTuple yann@1336: yann@1336: # All this for this single echo... :-( Sigh, I'll have to re-arrange things... yann@1336: echo "${CT_TARGET}" >&7