Commit graph

9 commits

Author SHA1 Message Date
Mike Swanson
6eef9be73a use python3 only for building
Python 2 is very near end-of-life, and Python3-compatible changes to a
few scripts introduced compatibility problems with 2.7 again.  It went
unnoticed for me since my system symlinks "python" to "python3", but
it broke the build on systems where that symlink is still python2.  At
this point in time, I feel it is worth targetting modern Python and
forgetting about 2.7.
2019-09-06 14:43:50 -07:00
Mike Swanson
a31450f5b9 Rename ULTDOOM/DOOM2 cpp defines to PHASE1/PHASE2
More self-consistent with out project, and those names dated before
Freedoom had a stronger identity.
2019-09-01 18:49:03 -07:00
Mike Swanson
d4c5b3ab48 simplecpp: keep blank lines 2019-09-01 17:24:25 -07:00
Mike Swanson
8835afef5f Copyright date bump and apply SPDX tags.
The tags are shorthand for the license of each file and avoid
copying the full license text into each one (and avoids having
to manually update the dates in each one...).
2017-02-15 16:41:53 -08:00
Mike Swanson
9b84cdebf0 Another year, another copyright date bump :) 2015-04-29 14:53:21 -07:00
Mike Swanson
dfe26e5607 Update copyright strings 2014-09-18 11:51:03 -07:00
Simon Howard
d6907ea974 build: Update Python scripts to work with Python 3.
Python 3 makes a number of changes to the language and breaks backward
compatibility with Python 2 in some places.  This change updates the
Python scripts used in the build system to work with Python 3,
although the updated scripts still run in Python 2 as well.  Most of
the changes are minor; the biggest changes are to the palette /
colormap generation scripts.

Signed-off-by: Simon Howard <fraggle@gmail.com>
2010-11-09 23:11:11 +00:00
Simon Howard
ece77ca176 Convert simplecpp script to Python. 2008-12-24 18:44:36 +00:00
Simon Howard
a1511aac95 Change build to use simplecpp for preprocessing, as this does not munge
up the configuration file.
2008-12-22 19:01:21 +00:00