freedoom
/
freedoom
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
freedoom/Makefile

131 lines
4.5 KiB
Makefile
Raw Normal View History

Update copyright strings
2014-09-18 11:51:03 -07:00
# Copyright (c) 2001-2014
Add copyrights, remove latest/ directory Adding copyright notices to critical files; some files which the project is not strictly dependent on, such as tools/cleanroom, are not tagged; many of these were meant for temporary use in assisting the development of Freedoom and their existence should probably be questioned. latest/ directory is removed since it's not critical to building the project, its use was for pre-sourceforge daily builds. Such a frequent building system may still be sought after, but this doesn't need to be in the repo ;) Signed-off-by: Mike Swanson <mikeonthecomputer@gmail.com>
2008-12-17 19:00:48 -08:00
# Contributors to the Freedoom project. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
#
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
# * Neither the name of the freedoom project nor the names of its
# contributors may be used to endorse or promote products derived from
# this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
# IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
# TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
# OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
# EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
# PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
# LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Import other stuff.
2006-05-09 09:20:42 -07:00
make: VERSION variable can be set either via git or the VERSION file Change up the shell line so that it can fallback on the VERSION file if building without a Git repository (eg, from a release tarball). Additionally, change the titlepic generation so that it uses this single instance of setting VERSION rather than doing its own thing.
2014-01-22 19:32:25 -08:00
VERSION=$(shell git describe 2>/dev/null || cat VERSION)
Add back WADS variable, set it to the correct value so that wads/filename.wad works as a build target.
2006-06-16 02:05:44 -07:00
WADS=wads
Change build to use simplecpp for preprocessing, as this does not munge up the configuration file.
2008-12-22 11:01:21 -08:00
CPP=scripts/simplecpp
Use the deutex installed on the system.
2006-05-09 09:54:05 -07:00
DEUTEX=deutex
quieten deutex
2008-12-26 09:47:14 -08:00
DEUTEX_BASIC_ARGS=-v0 -fullsnd -rate accept -rgb 0 255 255
Import other stuff.
2006-05-09 09:20:42 -07:00
DEUTEX_ARGS=$(DEUTEX_BASIC_ARGS) -doom2 bootstrap/
The Great IWAD Renaming: unique file names for Freedoom After some discussion and consensus[1], Freedoom's IWADs are now uniquely named independently of Doom's file names: * freedoom1.wad: Phase 1 * freedoom2.wad: Phase 2 The original intention was that Freedoom would be a complete drop-in replacement for Doom, so that you can just use Freedoom's doom2.wad rather than id Software's. What has happened, however, is that people often desire to have Freedoom installed alongside Doom, and try to uniquely identify it via filenames for multiplayer servers. This has resulted in lengthy lists of unofficial IWAD file names implemented by many engines to locate Freedoom, combined with gamers' personal opinions on just how they should be renamed. Even the Debian project, normally not one to modify upstream sources so drastically, has been renaming our doom2.wad to freedoom.wad, presumably so that Doom II can be installed simultaneously with game-data-packager. Given a free software engine, we can instead standardize on unique names apart from Doom and get the majority of engines in use changed over to these ones; users with engines that don't recognize the names can instead use the near-universal -iwad command-line parameter, or rename the files back to doom.wad or doom2.wad as needed. [1] http://www.doomworld.com/vb/freedoom/66856-bikeshedding-renaming-freedooms-iwads/
2014-01-11 20:21:51 -08:00
FREEDOOM1=$(WADS)/freedoom1.wad
FREEDOOM2=$(WADS)/freedoom2.wad
Build separate Zips for doom/doom2 and FreeDM Consensus shows that the change in 2014-01-07T06:34:47Z!mikeonthecomputer@gmail.com was a bit too extreme. Keep FreeDM as its own special thing, being much more focused on multiplayer than the other IWADs, as well as being the vanilla-compatible IWAD.
2014-01-07 17:45:41 -08:00
FREEDM=$(WADS)/freedm.wad
OBJS=$(FREEDM) $(FREEDOOM1) $(FREEDOOM2)
Import other stuff.
2006-05-09 09:20:42 -07:00
Stop building resource PWADs and "make dist" generates a single Zip The resource PWADs have been around for a very long time and dated from before Freedoom was capable of running as a complete IWAD on its own. Few people ever cared about these files, as evident by a lack of reports about freedoom_levels.wad not even being correct. Additionally, the separate Zips for each IWAD is gone. With that, Freedoom will be distributed as a single Zip file only that includes all of the subprojects.
2014-01-06 22:34:47 -08:00
all: $(OBJS)
Import other stuff.
2006-05-09 09:20:42 -07:00
subdirs:
build: Fix 'make -j' handling. Some build targets create multiple outputs, which can cause problems when doing parallel builds. Clean up the build system so that all subdir invocations come from the top-level Makefile and use $(MAKE). Also fix the FREEDOOM/FREEDM lumps to really include the version number by using $(shell ...) syntax.
2014-01-15 22:30:15 -08:00
$(MAKE) -C graphics/text
make: VERSION variable can be set either via git or the VERSION file Change up the shell line so that it can fallback on the VERSION file if building without a Git repository (eg, from a release tarball). Additionally, change the titlepic generation so that it uses this single instance of setting VERSION rather than doing its own thing.
2014-01-22 19:32:25 -08:00
$(MAKE) VERSION=$(VERSION) -C graphics/titlepic
build: Fix 'make -j' handling. Some build targets create multiple outputs, which can cause problems when doing parallel builds. Clean up the build system so that all subdir invocations come from the top-level Makefile and use $(MAKE). Also fix the FREEDOOM/FREEDM lumps to really include the version number by using $(shell ...) syntax.
2014-01-15 22:30:15 -08:00
$(MAKE) -C lumps/cph/misc-lumps
$(MAKE) -C lumps/genmidi
$(MAKE) -C lumps/dmxgus
$(MAKE) -C lumps/textures
Import other stuff.
2006-05-09 09:20:42 -07:00
# this is a useless dependency to force builds
force:
build: Fix 'make -j' handling. Some build targets create multiple outputs, which can cause problems when doing parallel builds. Clean up the build system so that all subdir invocations come from the top-level Makefile and use $(MAKE). Also fix the FREEDOOM/FREEDM lumps to really include the version number by using $(shell ...) syntax.
2014-01-15 22:30:15 -08:00
lumps/freedoom.lmp lumps/freedm.lmp: force
echo $(VERSION) > $@
Import other stuff.
2006-05-09 09:20:42 -07:00
# update wadinfo.txt
build: Fix Makefile dependencies for freedoom.lmp. The freedoom.lmp and freedm.lmp files must be created before the wadinfo-builder script is run, otherwise these lumps might get dummy substitutes.
2014-01-21 21:02:29 -08:00
wadinfo.txt: buildcfg.txt subdirs lumps/freedoom.lmp
Move scripts that are part of the build system into scripts/.
2008-12-24 10:50:30 -08:00
$(CPP) -P -DDOOM2 < $< | scripts/wadinfo-builder.py > $@
build: Fix Makefile dependencies for freedoom.lmp. The freedoom.lmp and freedm.lmp files must be created before the wadinfo-builder script is run, otherwise these lumps might get dummy substitutes.
2014-01-21 21:02:29 -08:00
wadinfo_phase1.txt: buildcfg.txt subdirs lumps/freedoom.lmp
Move scripts that are part of the build system into scripts/.
2008-12-24 10:50:30 -08:00
$(CPP) -P -DDOOM1 -DULTDOOM < $< | scripts/wadinfo-builder.py -dummy > $@
build: Fix Makefile dependencies for freedoom.lmp. The freedoom.lmp and freedm.lmp files must be created before the wadinfo-builder script is run, otherwise these lumps might get dummy substitutes.
2014-01-21 21:02:29 -08:00
wadinfo_phase2.txt: buildcfg.txt subdirs lumps/freedoom.lmp
The Great IWAD Renaming: unique file names for Freedoom After some discussion and consensus[1], Freedoom's IWADs are now uniquely named independently of Doom's file names: * freedoom1.wad: Phase 1 * freedoom2.wad: Phase 2 The original intention was that Freedoom would be a complete drop-in replacement for Doom, so that you can just use Freedoom's doom2.wad rather than id Software's. What has happened, however, is that people often desire to have Freedoom installed alongside Doom, and try to uniquely identify it via filenames for multiplayer servers. This has resulted in lengthy lists of unofficial IWAD file names implemented by many engines to locate Freedoom, combined with gamers' personal opinions on just how they should be renamed. Even the Debian project, normally not one to modify upstream sources so drastically, has been renaming our doom2.wad to freedoom.wad, presumably so that Doom II can be installed simultaneously with game-data-packager. Given a free software engine, we can instead standardize on unique names apart from Doom and get the majority of engines in use changed over to these ones; users with engines that don't recognize the names can instead use the near-universal -iwad command-line parameter, or rename the files back to doom.wad or doom2.wad as needed. [1] http://www.doomworld.com/vb/freedoom/66856-bikeshedding-renaming-freedooms-iwads/
2014-01-11 20:21:51 -08:00
$(CPP) -P -DDOOM2 < $< | scripts/wadinfo-builder.py -dummy > $@
build: Fix Makefile dependencies for freedoom.lmp. The freedoom.lmp and freedm.lmp files must be created before the wadinfo-builder script is run, otherwise these lumps might get dummy substitutes.
2014-01-21 21:02:29 -08:00
wadinfo_freedm.txt : buildcfg.txt subdirs lumps/freedoom.lmp lumps/freedm.lmp
Move scripts that are part of the build system into scripts/.
2008-12-24 10:50:30 -08:00
$(CPP) -P -DFREEDM < $< | scripts/wadinfo-builder.py -dummy > $@
Import other stuff.
2006-05-09 09:20:42 -07:00
%.wad.gz: %.wad
gzip < $< > $@
chmod o-r $<
md5sum $<.gz > $<.md5sum
rm -f $<
Sharewarendectomy Consensus that the "shareware" target was no longer necessary was reached long ago[1]. It just needs to actually get done. Thus: Makefile: - remove shareware targets buildcfg.txt, textures/combined.txt: - remove #ifdef/#ifndef SHAREWARE sections (almost entirely #ifndef) graphics/help2.gif: - remove symlink, help2 screen was shareware-only gitignore: - remove shareware files no longer built textures/shareware: - remove directory -- [1] http://www.doomworld.com/vb/freedoom/52758-removing-shareware/ . In particular, Jon wrote: >The original purpose of the shareware IWAD was to have a smaller set of >resources to target 100% completion of. That was probably met a long >time ago. More recently chungy wrote in <http://www.doomworld.com/vb/post/957707> >Removing the "demo"/"shareware" version of Freedoom has been discussed >but it's never been done. Actually it's a bit easier to just leave it >in than to remove it. (It'd be pretty easy to get rid of it anyway, but >nothing is really gained from it) Signed-off-by: RjY <rjy@users.sourceforge.net>
2011-04-10 02:07:34 -07:00
# deutex doesnt allow redirects for the filenames in the texture
# entries, so we have to change the texture1 symlink to point
# to whichever wad we are working on
Add FreeDM levels and freedm.wad IWAD build.
2006-06-03 16:18:12 -07:00
#---------------------------------------------------------
# freedm iwad
build: Fix Makefile dependencies for freedoom.lmp. The freedoom.lmp and freedm.lmp files must be created before the wadinfo-builder script is run, otherwise these lumps might get dummy substitutes.
2014-01-21 21:02:29 -08:00
$(FREEDM): wadinfo_freedm.txt subdirs
Generate required directories from make No longer keep these around via an empty .gitignore hack.
2014-01-06 21:51:17 -08:00
@mkdir -p $(WADS)
Add FreeDM levels and freedm.wad IWAD build.
2006-06-03 16:18:12 -07:00
rm -f $@
$(DEUTEX) $(DEUTEX_ARGS) -iwad -build wadinfo_freedm.txt $@
Import other stuff.
2006-05-09 09:20:42 -07:00
#---------------------------------------------------------
The Great IWAD Renaming: unique file names for Freedoom After some discussion and consensus[1], Freedoom's IWADs are now uniquely named independently of Doom's file names: * freedoom1.wad: Phase 1 * freedoom2.wad: Phase 2 The original intention was that Freedoom would be a complete drop-in replacement for Doom, so that you can just use Freedoom's doom2.wad rather than id Software's. What has happened, however, is that people often desire to have Freedoom installed alongside Doom, and try to uniquely identify it via filenames for multiplayer servers. This has resulted in lengthy lists of unofficial IWAD file names implemented by many engines to locate Freedoom, combined with gamers' personal opinions on just how they should be renamed. Even the Debian project, normally not one to modify upstream sources so drastically, has been renaming our doom2.wad to freedoom.wad, presumably so that Doom II can be installed simultaneously with game-data-packager. Given a free software engine, we can instead standardize on unique names apart from Doom and get the majority of engines in use changed over to these ones; users with engines that don't recognize the names can instead use the near-universal -iwad command-line parameter, or rename the files back to doom.wad or doom2.wad as needed. [1] http://www.doomworld.com/vb/freedoom/66856-bikeshedding-renaming-freedooms-iwads/
2014-01-11 20:21:51 -08:00
# phase 1 (udoom) iwad
Import other stuff.
2006-05-09 09:20:42 -07:00
build: Fix Makefile dependencies for freedoom.lmp. The freedoom.lmp and freedm.lmp files must be created before the wadinfo-builder script is run, otherwise these lumps might get dummy substitutes.
2014-01-21 21:02:29 -08:00
$(FREEDOOM1): wadinfo_phase1.txt subdirs
Generate required directories from make No longer keep these around via an empty .gitignore hack.
2014-01-06 21:51:17 -08:00
@mkdir -p $(WADS)
Import other stuff.
2006-05-09 09:20:42 -07:00
rm -f $@
textures: Rewrite Freedoom's texture build system. Stop using deutex's built-in texture builder and generate our own texture lumps. This is essential for compatibility reasons: the entries in the texture/pnames lumps must match the order of those in the original IWADs. Failure to match ordering means that some well-known WADs (eg. DTWID) would not work with Freedoom. This fixes #1, and also means that Freedoom can now be built in parallel using make's '-j' option.
2014-01-15 20:18:22 -08:00
$(DEUTEX) $(DEUTEX_ARGS) -iwad -lumps -patch -flats -sounds -musics -graphics -sprites -levels -build wadinfo_phase1.txt $@
Import other stuff.
2006-05-09 09:20:42 -07:00
Add makefile section to build doom.wad Signed-off-by: Mike Swanson <mikeonthecomputer@gmail.com>
2008-12-21 13:52:46 -08:00
#---------------------------------------------------------
The Great IWAD Renaming: unique file names for Freedoom After some discussion and consensus[1], Freedoom's IWADs are now uniquely named independently of Doom's file names: * freedoom1.wad: Phase 1 * freedoom2.wad: Phase 2 The original intention was that Freedoom would be a complete drop-in replacement for Doom, so that you can just use Freedoom's doom2.wad rather than id Software's. What has happened, however, is that people often desire to have Freedoom installed alongside Doom, and try to uniquely identify it via filenames for multiplayer servers. This has resulted in lengthy lists of unofficial IWAD file names implemented by many engines to locate Freedoom, combined with gamers' personal opinions on just how they should be renamed. Even the Debian project, normally not one to modify upstream sources so drastically, has been renaming our doom2.wad to freedoom.wad, presumably so that Doom II can be installed simultaneously with game-data-packager. Given a free software engine, we can instead standardize on unique names apart from Doom and get the majority of engines in use changed over to these ones; users with engines that don't recognize the names can instead use the near-universal -iwad command-line parameter, or rename the files back to doom.wad or doom2.wad as needed. [1] http://www.doomworld.com/vb/freedoom/66856-bikeshedding-renaming-freedooms-iwads/
2014-01-11 20:21:51 -08:00
# phase 2 (doom2) iwad
Add makefile section to build doom.wad Signed-off-by: Mike Swanson <mikeonthecomputer@gmail.com>
2008-12-21 13:52:46 -08:00
build: Fix Makefile dependencies for freedoom.lmp. The freedoom.lmp and freedm.lmp files must be created before the wadinfo-builder script is run, otherwise these lumps might get dummy substitutes.
2014-01-21 21:02:29 -08:00
$(FREEDOOM2): wadinfo_phase2.txt subdirs
Generate required directories from make No longer keep these around via an empty .gitignore hack.
2014-01-06 21:51:17 -08:00
@mkdir -p $(WADS)
Add makefile section to build doom.wad Signed-off-by: Mike Swanson <mikeonthecomputer@gmail.com>
2008-12-21 13:52:46 -08:00
rm -f $@
textures: Rewrite Freedoom's texture build system. Stop using deutex's built-in texture builder and generate our own texture lumps. This is essential for compatibility reasons: the entries in the texture/pnames lumps must match the order of those in the original IWADs. Failure to match ordering means that some well-known WADs (eg. DTWID) would not work with Freedoom. This fixes #1, and also means that Freedoom can now be built in parallel using make's '-j' option.
2014-01-15 20:18:22 -08:00
$(DEUTEX) $(DEUTEX_ARGS) -iwad -lumps -patch -flats -sounds -musics -graphics -sprites -levels -build wadinfo_phase2.txt $@
Add makefile section to build doom.wad Signed-off-by: Mike Swanson <mikeonthecomputer@gmail.com>
2008-12-21 13:52:46 -08:00
rename files from *.asc to *.adoc In a world ravaged by software that determines file type by the last part of the file's name, *.asc is somewhat troublesome given file managers that think these are PGP keys. Also GitHub won't render AsciiDoc without one of a few extensions, at least *.adoc is somewhat clearer and not as obnoxiously long as *.asciidoc
2014-05-02 18:42:19 -07:00
doc: BUILD-SYSTEM.adoc README.adoc
asciidoc BUILD-SYSTEM.adoc
asciidoc README.adoc
Makefile: add doc target to make pretty HTML-ized versions of documents Not adding to the all target of the Makefile (which is the default when make is invoked without parameters) as it would introduce an artificial build dependency on asciidoc; instead, "make doc" is to be used when you know you both want the *.html files and have asciidoc installed. Signed-off-by: Mike Swanson <mikeonthecomputer@gmail.com>
2009-07-30 15:05:56 -07:00
Build separate Zips for doom/doom2 and FreeDM Consensus shows that the change in 2014-01-07T06:34:47Z!mikeonthecomputer@gmail.com was a bit too extreme. Keep FreeDM as its own special thing, being much more focused on multiplayer than the other IWADs, as well as being the vanilla-compatible IWAD.
2014-01-07 17:45:41 -08:00
DISTDOCS=COPYING CREDITS README.html
# Due to convoluted reasons, the WADs must directly proceed the game name.
Makefile: dist target works again For now, Make is dependent on being run inside of the git repository, at least if something like `make VERSION=3.14` isn't used. Will be nice in the future if it can read from the VERSION file as a fallback.
2013-12-31 01:51:20 -08:00
dist: $(OBJS) doc
Build separate Zips for doom/doom2 and FreeDM Consensus shows that the change in 2014-01-07T06:34:47Z!mikeonthecomputer@gmail.com was a bit too extreme. Keep FreeDM as its own special thing, being much more focused on multiplayer than the other IWADs, as well as being the vanilla-compatible IWAD.
2014-01-07 17:45:41 -08:00
VERSION=$(VERSION) scripts/makepkgs freedm $(FREEDM) $(DISTDOCS)
VERSION=$(VERSION) scripts/makepkgs freedoom $(FREEDOOM1) $(FREEDOOM2) $(DISTDOCS)
Makefile: dist target works again For now, Make is dependent on being run inside of the git repository, at least if something like `make VERSION=3.14` isn't used. Will be nice in the future if it can read from the VERSION file as a fallback.
2013-12-31 01:51:20 -08:00
move towards using system CPP buildcfg.txt: rework OR relationship to be CPP-compliant remove tools/simplecpp Makefile: CPP=/usr/bin/cpp stop redundant rebuilds remove all from PHONY in lumps/cph/misc-lumps/Makefile clean up build output add a newline to lumps/cph/misc-lumps/colormap.pl add a clean target, to: ./Makefile ./lumps/Makefile ./lumps/cph/misc-lumps/Makefile
2006-06-12 13:36:32 -07:00
clean:
Makefile: add doc target to make pretty HTML-ized versions of documents Not adding to the all target of the Makefile (which is the default when make is invoked without parameters) as it would introduce an artificial build dependency on asciidoc; instead, "make doc" is to be used when you know you both want the *.html files and have asciidoc installed. Signed-off-by: Mike Swanson <mikeonthecomputer@gmail.com>
2009-07-30 15:05:56 -07:00
rm -f *.html deutex.log $(OBJS) \
The Great IWAD Renaming: unique file names for Freedoom After some discussion and consensus[1], Freedoom's IWADs are now uniquely named independently of Doom's file names: * freedoom1.wad: Phase 1 * freedoom2.wad: Phase 2 The original intention was that Freedoom would be a complete drop-in replacement for Doom, so that you can just use Freedoom's doom2.wad rather than id Software's. What has happened, however, is that people often desire to have Freedoom installed alongside Doom, and try to uniquely identify it via filenames for multiplayer servers. This has resulted in lengthy lists of unofficial IWAD file names implemented by many engines to locate Freedoom, combined with gamers' personal opinions on just how they should be renamed. Even the Debian project, normally not one to modify upstream sources so drastically, has been renaming our doom2.wad to freedoom.wad, presumably so that Doom II can be installed simultaneously with game-data-packager. Given a free software engine, we can instead standardize on unique names apart from Doom and get the majority of engines in use changed over to these ones; users with engines that don't recognize the names can instead use the near-universal -iwad command-line parameter, or rename the files back to doom.wad or doom2.wad as needed. [1] http://www.doomworld.com/vb/freedoom/66856-bikeshedding-renaming-freedooms-iwads/
2014-01-11 20:21:51 -08:00
./wadinfo.txt ./wadinfo_phase1.txt \
./wadinfo_phase2.txt ./wadinfo_freedm.txt \
FreeDM: add a FREEDM lump for source port detection Signed-off-by: Mike Swanson <mikeonthecomputer@gmail.com>
2010-09-15 13:55:03 -07:00
./lumps/freedoom.lmp \
textures: Only include patches needed by textures. Now that #1 is fixed, we can be certain that all patches needed for compatibility are definitely being included in the PNAMES lists. It therefore isn't necessary to include every patch in the patches/ directory in every WAD. Extend the build-textures script to generate a text file containing the list of PNAMES, and include this from the main config file. That way, each IWAD only gets the patches it explicitly needs.
2014-01-16 19:59:52 -08:00
./lumps/freedm.lmp
textures: Rewrite Freedoom's texture build system. Stop using deutex's built-in texture builder and generate our own texture lumps. This is essential for compatibility reasons: the entries in the texture/pnames lumps must match the order of those in the original IWADs. Failure to match ordering means that some well-known WADs (eg. DTWID) would not work with Freedoom. This fixes #1, and also means that Freedoom can now be built in parallel using make's '-j' option.
2014-01-15 20:18:22 -08:00
-rmdir $(WADS)
expand the clean target with a few more bits and pieces
2006-09-02 09:38:29 -07:00
build: Fix 'make -j' handling. Some build targets create multiple outputs, which can cause problems when doing parallel builds. Clean up the build system so that all subdir invocations come from the top-level Makefile and use $(MAKE). Also fix the FREEDOOM/FREEDM lumps to really include the version number by using $(shell ...) syntax.
2014-01-15 22:30:15 -08:00
$(MAKE) -C graphics/text clean
$(MAKE) -C graphics/titlepic clean
$(MAKE) -C lumps/cph/misc-lumps clean
$(MAKE) -C lumps/genmidi clean
$(MAKE) -C lumps/dmxgus clean
$(MAKE) -C lumps/textures clean