by MTrop (C) 2021
This is an example DoomMake project to show people how cool this stuff is.
Create a file called doommake.properties
and throw this stuff in there:
doommake.iwad=H:/Doom/iwads/DOOM2.WAD
doommake.run.exe=H:/DoomDev/Exes/ChocoDoom/chocolate-doom.exe
doommake.run.switch.file=-merge
You'll probably have to change those paths to the pertinent files. Note that .properties
files use backslashes differently (see the Wikipedia Page).
The first property is for the IWAD to use as a base for texture merging (DOOM2.WAD
),
and the other is for locating Chocolate Doom to test (if you don't use Chocolate Doom,
remove the last line).
This file is ignored in your repository.
Some directories/files in this project are ignored (or should be ignored) by repository "ignore" files:
/build Build directory.
/dist Distributables directory.
doommake.properties Project property override file.
This project requires the DoomTools toolchain for building it. Clone this project to a new folder and type:
doommake init
...In order to ensure everything has been prepped correctly (some directories or files may need extracting, downloading, or copying).
To clean the build folder, type:
doommake clean
To both initialize and build this project and its distributable archive:
doommake
To build the DeHackEd patch from DECOHack source:
doommake patch
To convert raw assets to Doom assets:
doommake convert
To build the assets WAD:
doommake assets
To build just the maps WAD:
doommake maps
To extract only the textures used by maps to a separate WAD file (if any):
doommake maptextures
To run this project (after setting the correct properties):
doommake run
To build all components:
doommake all
To build the full release:
doommake release