@@ -60,6 +60,15 @@
# The reason you might also want to install elsewhere is if you are going
# to package your shinny new toolchain for distribution.
+
+config CUSTOM_LOCATION_ROOT_DIR
+ string
+ depends on EXPERIMENTAL
+ prompt "directory containing custom source components"
+ help
+ This is the path CT-NG will attempt to use as a root for locating
+ local copies of source components (CUSTOM_LOCATION_ROOT_DIR/component)
+
config RM_RF_PREFIX_DIR
bool
prompt "| Remove the prefix dir prior to building"
@@ -516,6 +516,32 @@
return 1
}
+# This function gets the custom source from either a tarball or directory
+# Usage: CT_GetCustom custom_name <custom_location>
+CT_GetCustom() {
+ local custom_name="$1"
+ local custom_location="$2"
+
+ if [ ! -d "${custom_location}" ]; then
+ # We need to know the custom tarball extension,
+ # so we can create a properly-named symlink, which
+ # we use later on in 'extract'
+ case "${custom_location}" in
+ *.tar.bz2) custom_name="${custom_name}.tar.bz2";;
+ *.tar.gz|*.tgz) custom_name="${custom_name}.tar.gz";;
+ *.tar) custom_name="${custom_name}.tar";;
+ *) CT_Abort "Unknown extension for custom tarball '${custom_location}'";;
+ esac
+ CT_DoLog EXTRA "Using '${custom_name}' from local storage"
+ CT_DoExecLog DEBUG ln -sf "${custom_location}" \
+ "${CT_TARBALLS_DIR}/${custom_name}"
+ else
+ CT_DoLog EXTRA "Using '${custom_name}' from local storage"
+ CT_DoExecLog DEBUG ln -snf "${custom_location}" \
+ "${CT_SRC_DIR}/${custom_name}"
+ fi
+}
+
# This function saves the specified to local storage if possible,
# and if so, symlinks it for later usage
# Usage: CT_SaveLocal </full/path/file.name>