Difference between revisions of "Talk:Javascript Mess"
Jump to navigation
Jump to search
(→Emscripten attempt: new section) |
|||
| Line 1: | Line 1: | ||
== Devesine's Emscripten attempt == | |||
Shouldn't prevent anyone else from doing so as well, but I'm going to give the whole "whang it into Emscripten and see what explodes" thing a shot over the next few days. [[User:Devesine|Devesine]] 15:39, 3 November 2011 (UTC) | Shouldn't prevent anyone else from doing so as well, but I'm going to give the whole "whang it into Emscripten and see what explodes" thing a shot over the next few days. [[User:Devesine|Devesine]] 15:39, 3 November 2011 (UTC) | ||
=== current status === | |||
compiling, with some help from azakai and some headbanging. http://wizardmode.com/jsmess/logs/%23jsmess.11-04-17-12.log [[User:Devesine|Devesine]] 23:17, 4 November 2011 (UTC) | |||
Useful tips: | Useful tips: | ||
* Make sure you grab a fresh copy of llvm, clang, v8 (I'm not using spidermonkey yet) to point emscripten at | * Make sure you grab a fresh copy of llvm, clang, v8 (I'm not using spidermonkey yet) to point emscripten at | ||
* Build a non-debug version of llvm+clang - it will probably save a *lot* of time (there are a lot of files to compile) | * Build a non-debug version of llvm+clang - it will probably save a *lot* of time (there are a lot of files to compile) - `configure --enable-optimized` should do it | ||
* Build v8 by doing `scons d8` - using console=readline (or possibly snapshot=on or visibility=default) seems to break emscripten's compilation ability | * Build v8 by doing `scons d8` - using console=readline (or possibly snapshot=on or visibility=default) seems to break emscripten's compilation ability | ||
* You will need to build MAME/MESS natively, to have access to the tools ( cp mess-native/obj/osdmini/mess/build/* mess/obj/osdmini/mess/build ) | * You will need to build MAME/MESS natively, to have access to the tools ( cp mess-native/obj/osdmini/mess/build/* mess/obj/osdmini/mess/build ) | ||
* There are an awful lot of warnings that need to be made into non-errors to compile successfully - maybe some of them are indicitive of bugs in MAME/MESS? | * There are an awful lot of warnings that need to be made into non-errors to compile successfully - maybe some of them are indicitive of bugs in MAME/MESS? | ||
Revision as of 15:23, 5 November 2011
Devesine's Emscripten attempt
Shouldn't prevent anyone else from doing so as well, but I'm going to give the whole "whang it into Emscripten and see what explodes" thing a shot over the next few days. Devesine 15:39, 3 November 2011 (UTC)
current status
compiling, with some help from azakai and some headbanging. http://wizardmode.com/jsmess/logs/%23jsmess.11-04-17-12.log Devesine 23:17, 4 November 2011 (UTC)
Useful tips:
- Make sure you grab a fresh copy of llvm, clang, v8 (I'm not using spidermonkey yet) to point emscripten at
- Build a non-debug version of llvm+clang - it will probably save a *lot* of time (there are a lot of files to compile) - `configure --enable-optimized` should do it
- Build v8 by doing `scons d8` - using console=readline (or possibly snapshot=on or visibility=default) seems to break emscripten's compilation ability
- You will need to build MAME/MESS natively, to have access to the tools ( cp mess-native/obj/osdmini/mess/build/* mess/obj/osdmini/mess/build )
- There are an awful lot of warnings that need to be made into non-errors to compile successfully - maybe some of them are indicitive of bugs in MAME/MESS?