Etabeta thank you very much for your answer.
I was not expecting a very technical description from the point of view of C++ and their classes, etc., but I guess that was the answer to my question. I'm not a programmer. I would like more of a practical point of view.
I'm in the process of understanding, a very basic, the process of adding a clone Mame source code. And I got stuck when trying to understand the new field of the Macro "Game" and use it.
In the source code of older versions of Mame got add clones without too much trouble. (Studying some documents Mamedev)
Now I have understood that (you can correct me if I'm wrong):
In the field number 6 in GAME macro
- Driver_device: If you have a call to a "DRIVER_INIT_MEMBER" (do not need specific initialization)
- Pacman_state: variable (or its correct name) used in the initialization of the functions MACHINE_START, MACHINE_RESET, DRIVER_INIT, etc.
In the field number 7 GAME
-0: used with "driver_device" in field 6, for a not need for specific initialization.
maketrax / pacplus / eyes: variables used for call the specific initialization functions.
Apologies if I do not express things thoroughly ...sorry.
It would be correct, if I create a new init: pacman_state, rockman, in my MACRO:
GAME (1981, rockman, crush, pacman, maketrax, pacman_state, rockman, ROT90, "Alpha Denshi Co. / Samno Kural Electric, Ltd.", "Crush Roller (set 1)", GAME_SUPPORTS_SAVE)
From which it can call:
MACHINE_CONFIG_DERIVED static (pacman_state, rockman)
MCFG_CPU_MODIFY ("maincpu")
MCFG_CPU_CLOCK (6000000)
MACHINE_CONFIG_END
In this way I can create a new clone called "rockman", from the game "crush" modifying its initialization with a main CPU overclock.
(I know it should create the ROM START and add it to the master list of drivers, etc, etc)
I just want understand the driver inits and understand the process of creating a new clone.
Thank you very much and apologies for my ignorance on the matter.:P
|
Index 
Flat 
Re: A silly question about Mame drivers structure.
Reply
