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@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 2133 804a8f6d286a
child 2454 c70da6c50bdb
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 syntax: glob

     2 

     3 # Generated files

     4 Makefile

     5 ct-ng

     6 docs/ct-ng.1

     7 docs/ct-ng.1.gz

     8 paths.mk

     9 scripts/crosstool-NG.sh

    10 scripts/saveSample.sh

    11 scripts/showTuple.sh

    12 kconfig/conf

    13 kconfig/mconf

    14 kconfig/**.o

    15 kconfig/**.dep

    16 config.gen/

    17 .config

    18 

    19 # Temporaries

    20 .*.swp

    21 build.log

    22 .config.old

    23 

    24 # This is the place where toolchains are built

    25 .build/

    26 # .. and the legacy location

    27 targets/
crosstool-ng