> As for this project, although the page doesn't say so, I'm guessing it will be a DLL
> plus a 'front-end' portion?
libmame is the DLL part. There is no front-end portion, at least not of libmame. libmame is a way to enable using the MAME engine directly in other programs, including such things as a front-end, which in fact is what I am doing, although I am not really even close on my front-end yet.
> As some may remember, MESS was exactly like that and it caused all sorts of issues.
> When it was merged into one executable, those problems went away. So, Bryan, despite
> all the effort you've obviously put into this, I kinda doubt it would be accepted
> (once bitten, twice shy sort of thing). My personal view is that I don't care how the
> internals are put together as long as it works.
I wonder what the issues are. I have used libmame quite extensively and there haven't been any issues to speak of. And being able to run MAME directly within the front-end (in my case, segragated by a shared memory segment and process boundary, but the effect is the same) does open up the door for unique features.
|
Index 
Flat 
Re: libmame patch discussion please
Reply
