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 automake
3 CT_AUTOMAKE_VERSION=1.11.1
5 do_companion_tools_automake_get() {
6 CT_GetFile "automake-${CT_AUTOMAKE_VERSION}" \
7 {ftp,http}://ftp.gnu.org/gnu/automake
10 do_companion_tools_automake_extract() {
11 CT_Extract "automake-${CT_AUTOMAKE_VERSION}"
12 CT_DoExecLog ALL chmod -R u+w "${CT_SRC_DIR}/automake-${CT_AUTOMAKE_VERSION}"
13 CT_Patch "automake" "${CT_AUTOMAKE_VERSION}"
16 do_companion_tools_automake_build() {
17 CT_DoStep EXTRA "Installing automake"
18 mkdir -p "${CT_BUILD_DIR}/build-automake"
19 CT_Pushd "${CT_BUILD_DIR}/build-automake"
22 "${CT_SRC_DIR}/automake-${CT_AUTOMAKE_VERSION}/configure" \
23 --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"
25 CT_DoExecLog ALL make install