I have a different but related question that I also asked in the "merged build" thread but didn't get answered.
I always wondered, what is the point of building a "monolithic" exe and not have some of (or all) the main modules as separate dll in a subfolder?
Would possibly greatly help with end-user updates as possibly only SOME of the DLL change. Or indeed help with making almost what you ask... If asomeone has only some of the dll, he will be able to use MAME but with reduced functionality (eg. no "mechanical.dll" - although I am not saying I know what kind of dll "split" should be done, I am just giving an example).
So how come and MAME is not like that?
Cannot be done like that?
Is there a benefit in the current form?
---
NLS
|
Index 
Flat 
Re: Automated custom build installer/optimizer?
Reply
