Rooba
/
ReC98
mirror of https://github.com/nmlgc/ReC98.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ReC98/Makefile.mak

51 lines
1.4 KiB
Makefile
Raw Normal View History

Use a Makefile for the 16-bit part of the build process Well, that became unbearable pretty quickly. Not sure whether I'm doing all this Makefile business right, but this looks pretty nice. It doesn't really help much at this point though because the 32-bit part is still entirely separate and forces everything to rebuild all the time, but at least it aborts on C compiler errors.
2015-02-21 10:23:03 +00:00
# ReC98
# -----
# Makefile for the 16-bit part of the build process
[C decompilation] [th02/op] Title screen flashing animation
2015-02-21 13:13:58 +00:00
CFLAGS = -ls -Ilibs\master.lib\ -I. -Lbin\ -O -a2
Use a Makefile for the 16-bit part of the build process Well, that became unbearable pretty quickly. Not sure whether I'm doing all this Makefile business right, but this looks pretty nice. It doesn't really help much at this point though because the 32-bit part is still entirely separate and forces everything to rebuild all the time, but at least it aborts on C compiler errors.
2015-02-21 10:23:03 +00:00
TH01 = \zunsoft.com \op.exe \reiiden.exe \fuuin.exe
TH02 = \zuninit.com \zun_res.com \op.exe \main.exe \maine.exe
TH03 = \zunsp.com \res_yume.com \op.exe \main.exe \mainl.exe
TH04 = \res_huma.com \op.exe \main.exe \maine.exe
TH05 = \res_kso.com \op.exe \main.exe \maine.exe
all: th01 th02 th03 th04 th05
@echo Done. Find the executables in the bin\ subdirectory.
th01:: $(TH01:\=bin\th01\)
th02:: $(TH02:\=bin\th02\)
th03:: $(TH03:\=bin\th03\)
th04:: $(TH04:\=bin\th04\)
th05:: $(TH05:\=bin\th05\)
.obj.exe:
$(CC) $(CFLAGS) -ml $**
.obj.com:
tlink /t /3 $**
bin\th01\zunsoft.com: th01\zunsoft.c
[C decompilation] [th02/op] Title screen flashing animation
2015-02-21 13:13:58 +00:00
$(CC) $(CFLAGS) -mt -lt -nbin\th01\ $** masters.lib
[C decompilation] [th01] MDRV2 calls Still missing mdrv2_resident() though, which we currently can't slot in there due to that string constant constructor syntax. :/
2015-02-21 19:45:02 +00:00
bin\th01\op.exe: bin\th01\op.obj th01\op_11.c
$(CC) $(CFLAGS) -ml -3 -nbin\th01\ -eOP.EXE $**
bin\th01\reiiden.exe: bin\th01\reiiden.obj th01\main_16.c
$(CC) $(CFLAGS) -ml -3 -nbin\th01\ -eREIIDEN.EXE $**
[C decompilation] [th01] VRAM region copy via EGC The same function appears unused in TH02's MAINE.EXE. Separate commit because this was painful enough and we can link the C version into FUUIN.EXE right now.
2015-02-27 22:11:47 +00:00
bin\th01\fuuin.exe: bin\th01\fuuin.obj th01\fuuin_11.c th01\fuuin_13.c
$(CC) $(CFLAGS) -ml -3 -nbin\th01\ -eFUUIN.EXE @&&|
$**
|
[C decompilation] [th01] MDRV2 calls Still missing mdrv2_resident() though, which we currently can't slot in there due to that string constant constructor syntax. :/
2015-02-21 19:45:02 +00:00
[C decompilation] [th02/op] High score screen
2015-03-03 03:25:19 +00:00
bin\th02\op.exe: bin\th02\op.obj th02\op_03.c th02\op_04.c th02\op_05.c th02\op_06.c
[C decompilation] [th02/op] Shot type selection Oh, OK, so this is what the PC-98 GRCG is all about. You call grcg_setcolor(), and that puts the PC-98 hardware in some sort of "monochromatic mode". Then, you just write your pixels into any *single* one of the 4 VRAM bitplanes. This causes the hardware to automatically write to *all* bitplanes in such a way that the final palette index for each of the 8, 16, or 32 pixels you just wrote a 1 value to will actually end up to match the color you set earlier. Don't forget to call grcg_off() at the end though, or you can't draw any non-monochromatic graphics, heh.
2015-02-25 22:05:20 +00:00
$(CC) $(CFLAGS) -ml -Z -DGAME=2 -nbin\th02\ -eOP.EXE @&&|
$**
|
[C decompilation] [th02/maine] Rotating rectangle animation Small detour into MAINE.EXE because it has all the juicy algorithms that will explain the remaining unknown members of the highscore data structure, and there's this one code segment here we need to get out of the way first.
2015-02-28 21:37:40 +00:00
[C decompilation] [th02/maine] High score screen MAIN.EXE shares most of the code in this segment, but I can't remove it from there right now due to the weird ordering of the data segments in that executable… And yes, once again, those three seemingly random type casts in here are *necessary* to build a bit-perfect binary.
2015-03-02 05:20:28 +00:00
bin\th02\maine.exe: bin\th02\maine.obj th02\maine_04.c th02\maine_05.c
[C decompilation] [th02/maine] Rotating rectangle animation Small detour into MAINE.EXE because it has all the juicy algorithms that will explain the remaining unknown members of the highscore data structure, and there's this one code segment here we need to get out of the way first.
2015-02-28 21:37:40 +00:00
$(CC) $(CFLAGS) -ml -3 -Z -DGAME=2 -nbin\th02\ -eMAINE.EXE @&&|
$**
|