> >> First reason comes out of one of the responses from etabeta to NLS. As etabeta
> writes, "sub-builds" are not possible because, "if you don't build the whole tree,
> you could break some dependence".
> Your goal is to make combined build, and the reason is: you have to make combined
> build if you wanna make combined build. Your reason and the goal are the same, so
> it's non-sense, you have to tell us why do you want to make a combined build in the
> first place, what purpose "combined build" is supposed to serve?>>
I think that the confusion is that the original poster is suggesting that providing combined builds would help to ensure that changes in the source tree that were MAME or MESS specific would compile for both MAME and MESS build flavors. Thus the goal to achieve is greater robustness of the MAME/MESS code by testing combined builds more frequently.
That being said, I don't think the original poster realizes that combined builds are probably already tested in this way regularly, they're just not provided as downloadable, pre-built executables on the official download sites because of the other reasons pointed out in this thread.
So the goal, while commendable, is not likely to be furthered by combined builds.