>> Why in the fuck would you want to put users through all of that shit (setup.exe), when you can just decompress the exe file and run it?
You didn't read it properly. I said both *source code* and compiler can be distributed inside Windows binary, so to make it appear to user as simple as if they are installing some standard Windows application, while in fact when they press a button instead of installation there would be compilation.
The reason is that this would give everyone the kind of build they want, plus the build could be optimized for their particular CPU. Of course for this to work we first have to automatize "tiny.mak" thing or come up with some other method.
>> It works fine the way it is... either as MAME, MESS or combined. If you want fucked up custom builds, then YOU change the source code and build it yourself.
I did not ask you to do anything for me. It seems pretty obvious everyone here would get rid of mech and mahjong, at least, if they could, so the option to make custom builds and reduce the size of the binary seem far more desirable than adding MESS to the whole bloat and increasing the size of the binary even more.
>> Nothing that is 'extra' in MAME causes any problems. If you don't want to use artwork, etc., just don't use any.
All I'm really proposing here is to improve and automatize "tiny.mak" thing, an extra feature that does not cause any problems. If you don't want it, just don't use it.
Anyway, what do you say is the purpose combined MAME+MESS build is supposed to serve?