>> Apparently you haven't seen what we've been doing at all. #ifdef MESS hasn't existed for well over a year now. There is one single object-oriented core. You really think a unified build was possible with #ifdefs?
Ay, caramba! That's what I've been doing in my build for the last year too. What a terrible synchronization, my mistake.
I guess I missed out quite a bit then... errr, what "unified build" means? In summary what's the biggest change?
>> In case I haven't been clear enough about this: the source tree is being merged. That isn't even a debate.
I think people are talking about two different things while thinking to be talking about the same thing.
a.) separation/merge of source code
b.) separation/merge of the binaries
Someone should summarize what each of those really mean and what kind of difference it makes to end-users and developers.
For example, I don't care about binaries at all, even simple console script (.BAT) can be made to make it all very easy to compile and build whatever binary someone might wish, with neo-geo, maybe just some individual games, with bootlegs, with MESS, mechanical, gambling, mahjong... or without.
I do care about source code separation/merge. I don't wanna see any Artwork, Pacman or MESS related stuff in core input, core timing or core video handling module.
In other words, I want to see MESS source tree merged, but I also want MESS code in it's own separate files. Are we on the same frequency here?