> both projects are built over the same core, they share the same mailing list of
> developers, and the developers prefer to ship two separate executable and sources for
> end-users which don't compile by themselves.
> how is that a problem, when people capable of compiling a combined exe can already do
I am not sure how you talk about the whole team. Maybe you CAN talk about the whole team, I don't know. I think there are different voices though.
The problem is EXACTLY for people NOT capable of compiling a combined exe; which btw traditionally face some discrimination in some open source projects. In those projects (and I am not saying MAME is one of those) it is very common to face an almost racist comment "if you want it like that, do it yourself"... well having been on both sides in different phases of my IT life, I don't like that reply.
The problem also is that the way to build the combined exe is not (YET) official. Why? The best (? AFAIK) effort right now comes from a member that (again AFAIK) doesn't have the sympathy of some of the members of the team (for reasons we frankly do not care). This to an outsider (like me) seems like politics and just politics.
Anyway I think I have made my point (thank you for giving me the space to do so): Combined exe is the way to go. At least let it be an (official) option. I am 100% sure that in the end it is going to be the default.