Also set CT_DEBUGROOT_DIR for non sysroot-ed toolchains.
In the non-sysroot-ed case, the debuf-root directory would not be set;
debug tools would have been installed God-only-knows-where...
Spotted by Bart van der Meulen <bartvdrmeulen@gmail.com>.
6 # Parse the tools' paths configuration
7 . "${CT_LIB_DIR}/paths.mk"
9 # We'll need the stdout later, save it
12 # Parse the common functions
13 . "${CT_LIB_DIR}/scripts/functions"
15 # Don't care about any log file
17 rm -f "${tmp_log_file}"
19 # Parse the configuration file
22 # Parse architecture and kernel specific functions
23 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
24 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
29 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...
30 echo "${CT_TARGET}" >&7