Skip to content

Commit

Permalink
[Build] 16-bit: Don't explictly specify the .OBJ extension in TASM rules
Browse files Browse the repository at this point in the history
If the output file already exists, TASM interprets a filename with
extension as a directory, and then concatenates the implicitly
generated output file name to that path… yup.

Part of P0001, funded by GhostPhanom.
  • Loading branch information
nmlgc committed Sep 3, 2020
1 parent 61358c1 commit 51b775b
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions Makefile.mak
Original file line number Diff line number Diff line change
Expand Up @@ -25,20 +25,20 @@ th05:: $(TH05:\=bin\th05\)
# Third-party libraries
# ---------------------
bin\piloadc.obj: libs\piloadc\piloadc.asm
$(AS) $(AFLAGS) $**, $@
$(AS) $(AFLAGS) $**, $*
# ---------------------

{th05}.asm{bin\th05}.obj:
$(AS) $(AFLAGS) /dGAME=5 $**, $@
$(AS) $(AFLAGS) /dGAME=5 $**, $(@R)

# Shared TH04/TH05 assembly units
# -------------------------------
# Need to go into separate .obj directories since they will have different
# AFLAGS per game.
{th04}.asm{bin\th04}.obj:
$(AS) $(AFLAGS) /dGAME=4 $**, $@
$(AS) $(AFLAGS) /dGAME=4 $**, $(@R)
{th04}.asm{bin\th05}.obj:
$(AS) $(AFLAGS) /dGAME=5 $**, $@
$(AS) $(AFLAGS) /dGAME=5 $**, $(@R)
# -------------------------------

.obj.exe:
Expand Down

0 comments on commit 51b775b

Please sign in to comment.