#MAC MSX EMULATOR CODE#
I just think it's important to stress that we use a lot of code from other people, but only if the authors gave permission.
#MAC MSX EMULATOR PORTABLE#
Those libraries are ported to a lot of systems already: there aren't many systems on which SDL doesn't run (it runs on PDAs, game consoles etc), GCC is the most portable (cross) compiler out there and the required libraries TCL, libpng and libxml2 are widely ported as well. For porting fMSX you have to write platform specific video, audio and input code and then only compile fMSX itself, while for porting openMSX you don't have to write any code, but you have to compile several libraries before you can compile openMSX itself. Whether fMSX or openMSX is easier to port depends on your point of view. David started with some designs to improve fMSX, but with Marat being the only person working on the fMSX code base, it seemed unlikely those would ever be implemented in fMSX. The most important one is that the interleaving of different devices is done with static time slots (of 1/256th frame) instead of dynamically (like openMSX's EmuTime concept). However, there are certain limitations in the design of fMSX that are impossible to overcome without major changes. fMSX got me interested in MSX emulation and it taught me how an emulator works. I think most openMSX developers have played with the fMSX code. The V9938 command engine started with Alex Wulm's code, just as fMSX, and although we made several improvements, the basic design is still the same as the original code from Alex.Īlthough we're not using fMSX code, we were influenced by fMSX a lot. However, the Z80 engine started with Marcel de Kogel's code, which is also used in fMSX I think this code has been fully rewritten by now. OpenMSX did not at any point contain fMSX code.
0 kommentar(er)
