> Guess what? It already is. Drivers can be EASILY removed before compilation. There's
> no point in separating drivers out into, say, DLL files post-compilation. RAM usage
> wouldn't change, CPU usage wouldn't change.
I was not talking about separating drivers, they are already separated. I was talking about scanlines, artwork, bezels, cheats, save states... anything that is not necessary to reproduce what actual PCB does, it's called "emulation".
HLSLSHL effects, bezels and stuff like that is not what PCBs do, it's what monitors made of glass do and what cabinets made of wood do, that's not "emulation", it's "simulation".
You have to decide is core MAME about documenting electronic s (PCBs) and emulation, or is it about simulation and documenting monitor quirks and cabinet decoration. I think core MAME shold be only about emulation and not about simulation, which is welcome addition, but is sufficient to be optional rather then default for all the reasons I mentioned in the post above.
Also MESS is not separated from MAME completely as it could be, like Pacman driver is. All these things I say could be separated from MAME core just like game drivers are.
Edited by LazyCat (05/07/12 05:45 PM)
|
Index 
Flat 
Re: Combined build
Reply
