garyopa
12-30-2011, 12:47 PM
Google Employee Does Case Study, 'Ports MAME to Native Client'
http://www.maxconsole.com/maxconsole/contents/RKSID00000000000000000424/icon_xl.jpg
Love to Play 'Retro' Games? -- Now thanks to a smart Google Cookie by the name of Robert Muth, you can just use their 'Chrome Browser' now to play all of them, instead of setting up a MAME build!
"It not the fact that is another 'emulator' is running in Chrome. - It is the fact on 'whom' did the port, it was done by GOOGLE themselves. - A employee on COMPANY TIME, releasing it on their GOOGLE DEVELOPMENT website!"
Google has an history of allowing their staff to work on 'cool ideas', and in this case, they ended up porting over the 'Multiple Arcade Machine Emulator' (aka) MAME which basically allows you to run many of the old-school retro classic gaming machines now on your Chrome Browser!
This article describes our experience porting Multiple Arcade Machine Emulator (MAME (http://mamedev.org/)), an emulator for a large number of classic arcade games, to Native Client. We discuss a number of topics in detail, such as our overall porting strategy, how we dealt with newlib incompatibilities, and how we handled binaries that are built and run as part of the build process. We do not discuss topics such as how to load resources in Native Client or how to port SDL games to Native Client (the articles listed in the Links (https://developers.google.com/native-client/community/porting/MAME#Links) section cover those topics). Our port is based on MAME version 0.143 (http://mamedev.org/downloader.php?file=releases/mame0143s.zip) (zip file).
Note: This document describes how we ported MAME using tools on the Linux platform. The resulting code runs in the Google Chrome browser on all currently supported Native Client platforms (Windows, Mac, and Linux).
The port of MAME was relatively challenging; combined with figuring out how to port SDL-based games and load resources in Native Client, the overall effort took us about 4 days to complete. The core port resulted in a diff of about 1200 lines, changing about 20 files.
Sounds simple, but it was not an easy feat, and now Google is one step closer to having an 'Gaming Machine' of their own!
NEWS SOURCE: Porting MAME to Native Client (via) Google (https://developers.google.com/native-client/community/porting/MAME)
http://www.maxconsole.com/maxconsole/contents/RKSID00000000000000000424/icon_xl.jpg
Love to Play 'Retro' Games? -- Now thanks to a smart Google Cookie by the name of Robert Muth, you can just use their 'Chrome Browser' now to play all of them, instead of setting up a MAME build!
"It not the fact that is another 'emulator' is running in Chrome. - It is the fact on 'whom' did the port, it was done by GOOGLE themselves. - A employee on COMPANY TIME, releasing it on their GOOGLE DEVELOPMENT website!"
Google has an history of allowing their staff to work on 'cool ideas', and in this case, they ended up porting over the 'Multiple Arcade Machine Emulator' (aka) MAME which basically allows you to run many of the old-school retro classic gaming machines now on your Chrome Browser!
This article describes our experience porting Multiple Arcade Machine Emulator (MAME (http://mamedev.org/)), an emulator for a large number of classic arcade games, to Native Client. We discuss a number of topics in detail, such as our overall porting strategy, how we dealt with newlib incompatibilities, and how we handled binaries that are built and run as part of the build process. We do not discuss topics such as how to load resources in Native Client or how to port SDL games to Native Client (the articles listed in the Links (https://developers.google.com/native-client/community/porting/MAME#Links) section cover those topics). Our port is based on MAME version 0.143 (http://mamedev.org/downloader.php?file=releases/mame0143s.zip) (zip file).
Note: This document describes how we ported MAME using tools on the Linux platform. The resulting code runs in the Google Chrome browser on all currently supported Native Client platforms (Windows, Mac, and Linux).
The port of MAME was relatively challenging; combined with figuring out how to port SDL-based games and load resources in Native Client, the overall effort took us about 4 days to complete. The core port resulted in a diff of about 1200 lines, changing about 20 files.
Sounds simple, but it was not an easy feat, and now Google is one step closer to having an 'Gaming Machine' of their own!
NEWS SOURCE: Porting MAME to Native Client (via) Google (https://developers.google.com/native-client/community/porting/MAME)