> A tiny compile will only do one game. However, that's all I know, sorry.
>
> If you look at the makefile, it may be self-explanatory.
Actually they changed it a few betas ago and you can now compile multiple
drivers. Basically you update "src\tiny.mak" with the drivers, CPUs and
object files and do a "make TARGET=tiny". The available CPUs and object
files are listed in "src\mame.mak".
It's hard to guess in advance what CPUs and object files are needed so
normally I just put in the driver source file, comment out all CPUs and
do a make and see what's undefined.
dkong is one of those that's quite messy because of clones on scramble
hardware. The following is what's needed in "src\tiny.mak" to do a tiny
compile for dkong:
# a tiny compile is without Neogeo games
COREDEFS += -DTINY_COMPILE=1
COREDEFS += -DTINY_NAME="driver_dkong"
COREDEFS += -DTINY_POINTER="&driver_dkong"
# uses these CPUs
CPUS+=N2A03@
CPUS+=I8035@
CPUS+=Z80@
CPUS+=S2650@
# uses these SOUNDs
SOUNDS+=NES@
SOUNDS+=DAC@
SOUNDS+=SAMPLES@
SOUNDS+=AY8910@
SOUNDS+=TMS5110@
SOUNDS+=CUSTOM@
OBJS = $(OBJ)/drivers/dkong.o $(OBJ)/sndhrdw/dkong.o $(OBJ)/vidhrdw/dkong.o
\
$(OBJ)/drivers/scramble.o $(OBJ)/machine/scramble.o
$(OBJ)/sndhrdw/scramble.o \
$(OBJ)/vidhrdw/galaxian.o $(OBJ)/drivers/scobra.o
$(OBJ)/drivers/amidar.o \
$(OBJ)/drivers/frogger.o $(OBJ)/sndhrdw/frogger.o
$(OBJ)/vidhrdw/frogger.o \
$(OBJ)/vidhrdw/amidar.o $(OBJ)/drivers/cvs.o
$(OBJ)/vidhrdw/cvs.o \
$(OBJ)/vidhrdw/s2636.o $(OBJ)/drivers/cclimber.o
$(OBJ)/sndhrdw/cclimber.o \
$(OBJ)/vidhrdw/cclimber.o
# MAME specific core objs
COREOBJS += $(OBJ)/driver.o $(OBJ)/cheat.o
iob
|