You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

234 lines
4.2 KiB

# Ignore editor artefacts
# Top level excludes
10 years ago
Refactor file writing - introduce template driven file writing apps/ and tools/c_rehash are built from template files. So far, this was done by Configure, which created its own problems as it forced everyone to reconfigure just because one of the template files had changed. Instead, have those files created as part of the normal build in apps/ and in tools/. Furthermore, this prepares for a future where Configure may produce entirely other build files than Makefile, and the latter can't be guaranteed to be the holder of all information for other scripts. Instead, (described below) becomes the center of configuration information. This introduces a few new things: %config a hash table to hold all kinds of configuration data that can be used by any other script. a perl module that Configure writes. It currently holds the hash tables %config and %target. util/ a script that takes a template on STDIN and outputs the result after applying configuration data on it. It's supposed to be called like this: perl -I$(TOP) -Mconfigdata < template > result or perl -I$(TOP) -Mconfigdata templ1 templ2 ... > result Note: util/ requires Text::Template. As part of this changed, remove a number of variables that are really just copies of entries in %target, and use %target directly. The exceptions are $target{cflags} and $target{lflags}, they do get copied to $cflags and $lflags. The reason for this is that those variable potentially go through a lot of changes and would rather deserve a place in %config. That, however, is for another commit. Reviewed-by: Rich Salz <> Reviewed-by: Richard Levitte <>
8 years ago
# Links under apps
# Auto generated headers
# Auto generated doc files
# Auto generated der files
# error code files
# Executables
# Certain files that get created by tests on the fly
# Fuzz stuff.
# Anything without an extension is an executable on Unix, so we keep files
# with extensions. And we keep the corpora subddir versioned as well.
# Anything more generic with extensions that should be ignored will be taken
# care of by general ignores for those extensions (*.o, *.obj, *.exe, ...)
# Misc auto generated files
# Windows (legacy)
# Files created on other branches that are not held in git, and are not
# needed on this branch
# Generated docs directories
##### Generic patterns
# Auto generated assembly language source files
# Object files
# editor artefacts
# Certificate symbolic links
# All kinds of libraries and executables
# Misc generated stuff
# Windows manifest files