Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
.hgignore
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
parent 2836 1c4f3be68a6d
permissions -rw-r--r--
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 syntax: glob

     2 

     3 # Generated files

     4 configure

     5 autom4te.cache

     6 config.log

     7 config.status

     8 Makefile

     9 *ct-ng*

    10 docs/*ct-ng*.1

    11 docs/*ct-ng*.1.gz

    12 paths.mk

    13 paths.sh

    14 scripts/crosstool-NG.sh

    15 scripts/saveSample.sh

    16 scripts/showTuple.sh

    17 kconfig/conf

    18 kconfig/?conf

    19 kconfig/**.o

    20 kconfig/**.dep

    21 kconfig/lex.backup

    22 kconfig/lex.zconf.c

    23 kconfig/zconf.hash.c

    24 kconfig/zconf.tab.c

    25 config/configure.in

    26 config.gen/

    27 .config

    28 .config.2

    29 

    30 # Temporaries

    31 .*.swp

    32 build.log

    33 .config.old

    34 

    35 # This is the place where toolchains are built

    36 .build/

    37 # .. and the legacy location

    38 targets/
crosstool-ng