mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2024-12-18 20:37:56 +00:00
7bfa4139ad
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>
28 lines
365 B
Plaintext
28 lines
365 B
Plaintext
syntax: glob
|
|
|
|
# Generated files
|
|
Makefile
|
|
ct-ng
|
|
docs/ct-ng.1
|
|
docs/ct-ng.1.gz
|
|
paths.mk
|
|
scripts/crosstool-NG.sh
|
|
scripts/saveSample.sh
|
|
scripts/showTuple.sh
|
|
kconfig/conf
|
|
kconfig/mconf
|
|
kconfig/**.o
|
|
kconfig/**.dep
|
|
config.gen/
|
|
.config
|
|
|
|
# Temporaries
|
|
.*.swp
|
|
build.log
|
|
.config.old
|
|
|
|
# This is the place where toolchains are built
|
|
.build/
|
|
# .. and the legacy location
|
|
targets/
|