|
> > But the binaries are never portable, of course. The source code still could be > - > > I have done this before. > > > > It is potentially as portable as the current system. > > How? Please enlighten me?
It's not too hard. If you look into cygwin and mingw, they can be used to treat DLLs much like shared objects on unix systems. Beyond that, some per-architecture macros and such are simple enough to cleanly implement. > And how exactly would you handle the DOS port? Or the Kodak port?
I wouldn't have them use dynamic loading, of course. Problem solved.
Or have you never seen a project that can be compiled either way? There are thousands out there.
> Or the Dreamcast port? Or the EPOC version?
See above. > And who would voluteer to rewrite the entire MAME source code (all 2000 > drivers). Yourself? Now you are getting petty. If I get less busy, I might consider it. It's not as if you need individual effort on each driver, any more than you do to convert the linefeeds. (Well, more, but it's mostly a template process). And just because I'm not doing it myself right now does not mean it is not a good idea.
- Rob
|