[Build] 16-bit: Don't explictly specify the .OBJ extension in TASM rules

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.
This commit is contained in:
nmlgc 2020-09-01 03:02:16 +02:00
parent 61358c1082
commit 51b775bd41
1 changed files with 4 additions and 4 deletions

View File

@ -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: