| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
possibility to disable it (based on patch by MJP)
|
|
|
|
pkg-config
|
|
|
|
-D_FORTIFY_SOURCE=2 -O1
|
|
support it
|
|
directly without a trip through the window messaging system.
|
|
|
|
ldflags by spaces, thus only call it with one
|
|
non-const iconv declaration.
|
|
|
|
|
|
explain its use in the readme
|
|
|
|
subversion repository in case someone has a sparse tags checkout. In that case the .svn folder misses from the $ROOT_DIR because it is in the $ROOT_DIR/.. (i.e. tags) folder
|
|
|
|
|
|
|
|
|
|
newer than 2.3
|
|
|
|
value), which clearly nobody uses, as it has been broken .... for a while
|
|
those who expect all software to follow GNU guidelines
|
|
really needed anyway
|
|
builds
|
|
helper binaries such as depend, strgen and settingsgen
|
|
compiled for the build enviroment
|
|
versioning scheme since ICU 49
|
|
aren't needed anymore with newer GRFCodec/NFORenum
|
|
GRFCodec determine the best compression
|
|
|
|
|
|
reduce the chance that it happens significantly with betas/RCs/nightlies by doing the same as is done for stable releases: check the NewGRF version of server vs client.
Previously this check was not done for nightlies/betas/RCs due to missing versioning information in the source tarballs, but they have that for a while now. So just force the NewGRF version check for all versions, and remove the broken --revision configure option
|
|
when grfcodec/nforenum were not usable.
|
|
|
|
configure, including a version check so a proper error can be given when a too old grfcodec or nforenum is used
|
|
parts some compilers failed at, are integrated in other parts of the code now too
|
|
prevent some invalid GCC warnings
|
|
many useless warnings with GCC 4.7
|
|
|
|
without using it (Rubidium)
|
|
|
|
config.log
|
|
unusable
|
|
with LTO use number of processes passed to make -j
|
|
compiler can do more optimisations
|
