scripts/addToolsVersion: properly handle .in vs. .in.2
While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).
Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.
So, for each tool, we need to explicitly know what file to munge.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
1 # Build script for autoconf
3 CT_AUTOCONF_VERSION=2.65
5 do_companion_tools_autoconf_get() {
6 CT_GetFile "autoconf-${CT_AUTOCONF_VERSION}" \
7 {ftp,http}://ftp.gnu.org/gnu/autoconf
10 do_companion_tools_autoconf_extract() {
11 CT_Extract "autoconf-${CT_AUTOCONF_VERSION}"
12 CT_DoExecLog ALL chmod -R u+w "${CT_SRC_DIR}/autoconf-${CT_AUTOCONF_VERSION}"
13 CT_Patch "autoconf" "${CT_AUTOCONF_VERSION}"
16 do_companion_tools_autoconf_build() {
17 CT_DoStep EXTRA "Installing autoconf"
18 mkdir -p "${CT_BUILD_DIR}/build-autoconf"
19 CT_Pushd "${CT_BUILD_DIR}/build-autoconf"
21 # Ensure configure gets run using the CONFIG_SHELL as configure seems to
22 # have trouble when CONFIG_SHELL is set and /bin/sh isn't bash
24 # http://www.gnu.org/software/autoconf/manual/autoconf.html#CONFIG_005fSHELL
26 CT_DoExecLog CFG ${CONFIG_SHELL} \
27 "${CT_SRC_DIR}/autoconf-${CT_AUTOCONF_VERSION}/configure" \
28 --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"
30 CT_DoExecLog ALL make install