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 ltrace
3 do_debug_ltrace_get() {
4 CT_GetFile "ltrace_${CT_LTRACE_VERSION}.orig" .tar.gz \
5 {ftp,http}://ftp.de.debian.org/debian/pool/main/l/ltrace/
6 # Create a link so that the following steps are easier to do:
7 CT_Pushd "${CT_TARBALLS_DIR}"
8 ltrace_ext=$(CT_GetFileExtension "ltrace_${CT_LTRACE_VERSION}.orig")
9 ln -sf "ltrace_${CT_LTRACE_VERSION}.orig${ltrace_ext}" \
10 "ltrace-${CT_LTRACE_VERSION}${ltrace_ext}"
14 do_debug_ltrace_extract() {
15 CT_Extract "ltrace-${CT_LTRACE_VERSION}"
16 CT_Patch "ltrace" "${CT_LTRACE_VERSION}"
19 do_debug_ltrace_build() {
22 CT_DoStep INFO "Installing ltrace"
24 CT_DoLog EXTRA "Copying sources to build dir"
25 CT_DoExecLog ALL cp -av "${CT_SRC_DIR}/ltrace-${CT_LTRACE_VERSION}" \
26 "${CT_BUILD_DIR}/build-ltrace"
27 CT_Pushd "${CT_BUILD_DIR}/build-ltrace"
29 CT_DoLog EXTRA "Configuring ltrace"
30 # ltrace-0.5.3, and later, don't use GNU Autotools configure script anymore
31 if [ "${CT_LTRACE_0_5_3_or_later}" = "y" ]; then
32 case "${CT_ARCH}:${CT_ARCH_BITNESS}" in
33 x86:32) ltrace_host="i386";;
34 x86:64) ltrace_host="x86_64";;
35 powerpc:*) ltrace_host="ppc";;
36 mips:*) ltrace_host="mipsel";;
37 *) ltrace_host="${CT_ARCH}";;
40 CC="${CT_TARGET}-${CT_CC}" \
41 AR="${CT_TARGET}-ar" \
42 HOST="${ltrace_host}" \
43 HOST_OS="${CT_TARGET_KERNEL}" \
44 CFLAGS="${CT_TARGET_CFLAGS}" \
45 ./configure --prefix=/usr
54 CT_DoLog EXTRA "Building ltrace"
57 CT_DoLog EXTRA "Installing ltrace"
58 CT_DoExecLog ALL make DESTDIR="${CT_DEBUGROOT_DIR}" install