#jsmess 2017-03-13,Mon

↑back Search

Time Nickname Message
00:57 🔗 SketchCow I'm home!
00:58 🔗 SketchCow bai Vito` db48x (Folks who worked directly on Emularity) is there an objection to a WebAssembly logo before it starts the programs, when they're in webassembly?
00:59 🔗 SketchCow I was thinking we could br real ambassadors for it
00:59 🔗 bai no, I think that's great
00:59 🔗 Vito` instead of the emulator logo?
00:59 🔗 SketchCow I don't want to do it unless all of you sign off, since you put work in
00:59 🔗 bai I would say in addition
00:59 🔗 SketchCow Either way.
01:00 🔗 SketchCow Either an additional splash before running, or changing the loading screen
01:00 🔗 SketchCow I just mean the idea right now, not the implementation
01:00 🔗 Vito` from an informational perspective, I think it makes sense as a status item, maybe the first one, to indicate it's using WebAssembly (or not)
01:01 🔗 SketchCow That leaves db48x
01:02 🔗 SketchCow Also, did we have an opinion to shared aws instance
01:02 🔗 SketchCow Documented and scripted so we can turn one into a box if we need several
01:03 🔗 bai aws is fine, just remember when allocating the disk space that you'll probably need a good size
01:03 🔗 Vito` and probably not the lowest-end of IO performance
01:03 🔗 Vito` if you do it you can close this issue: https://github.com/jsmess/jsmess/issues/97
01:03 🔗 bai I had a 15gb virtual drive set up for my vm and it wasn't enough, clang was taking 14gb by itself
01:04 🔗 SketchCow Poor yoz, he got so busy
01:04 🔗 SketchCow Yeah, we'll do this one
01:04 🔗 bai eh, I wouldn't worry too much about the io performance, we don't really care if the build takes 10 minutes vs 15
01:05 🔗 bai the thing you do want is multiple cores
01:05 🔗 bai so you want to be able to just spin this up on a powerful system, build, and throw it away as fast as possible
01:06 🔗 bai (within the hour)
01:07 🔗 bai it doesn't make sense to pay for a box that's always-on and also capable of building this stuff the one day every few months we go on a building spree
01:08 🔗 bai but it should be simple to just spin it up, compile, and shut down
01:10 🔗 SketchCow Playing Windows 3.1
01:10 🔗 SketchCow Can you compile a couple of the others in the WASM set on metacade? I'd like to see the speed.
01:11 🔗 bai ok, yeah I'l redo builds for all of them
01:17 🔗 SketchCow Tell me how this sounds as a general plan for the builds.
01:18 🔗 SketchCow I will make an amazon instance, and write a script, which then adds the needed components for a build system.
01:18 🔗 SketchCow Then we do rounds of error checking, etc.
02:23 🔗 db48x Vito`: example_ia.html works for me
02:23 🔗 db48x Vito`: https://github.com/db48x/emularity/blob/master/example_ia.html
02:23 🔗 db48x SketchCow: WebAssembly logo will be nice
02:24 🔗 SketchCow Great
02:24 🔗 SketchCow Unanimous
02:24 🔗 Vito` db48x: example_ia doesn't work for me with those two other objects
02:25 🔗 SketchCow https://github.com/carlosbaraza/web-assembly-logo
02:25 🔗 Vito` db48x: and example_ia doesn't work for me in phantomjs with the object it specifies by default
02:26 🔗 db48x Vito`: I get a 503 from the server on Oregon Trail as well...
02:27 🔗 Vito` db48x: right, but it works fine going to the regular archive.org url for it
02:28 🔗 db48x maybe cors.archive.org is borked
02:28 🔗 db48x regular archive.org page doesn't use cors.archive.org
02:29 🔗 db48x SketchCow: for a build machine we should use a proper configuration system like propellor, rather than writing our own system
02:31 🔗 db48x Vito`: for now I suggest testing with Pitfall_Activision_1982
02:31 🔗 db48x not sure why it would fail on one but not the other though
02:32 🔗 SketchCow You just outstripped my knowledge
02:32 🔗 SketchCow :)
02:32 🔗 SketchCow I'm always trying to take the load off people, but I can only work with my limited skills
02:32 🔗 SketchCow I do everything with scripts
02:32 🔗 SketchCow I'm willing to be team secretary
02:34 🔗 bai mostly that's what all these various container/system management things boil down to, is configs and scripts which automate the setup, build, and tear-down processes of systems configured for a certain task
02:34 🔗 db48x technically a configuration management system _is_ a script, but it's generally one that someone else went to the trouble of bullet-proofing
02:34 🔗 bai like configuring the system to automatically install this set of packages, then pull down these github reps and build them, then do whatever with the result
02:34 🔗 bai repos*
02:34 🔗 SketchCow I'm just saying I can't do it
02:35 🔗 SketchCow But I'll fund AWS or other machinery
02:35 🔗 SketchCow By the way, you all know I had a heart attack, right
02:36 🔗 SketchCow (This is unrelated to a container setup)
02:36 🔗 bai if db48x has a preference I say we go with that, I'm not familiar with that particular system but if he can set up the basic config, I can help with getting the system that it builds working
02:37 🔗 bai then on your end it's just a matter of loading that into aws, and hooking up whatever you want to do with the built files when they're done
02:38 🔗 bai eg, a script which uploads to IA
02:38 🔗 Vito` if you're on AWS, you shouldn't be using a build system, you should be making an image
02:38 🔗 Vito` should just be able to spin up an AMI that has everything set up already
02:38 🔗 bai see I have no opinion on what system is used to do this, I'll let people who do have opinions figure that part out
02:39 🔗 bai whatever it is, it's a set of packages and a couple short scripts
02:39 🔗 SketchCow My specific interest is easy recreation by people outside our happy team
02:39 🔗 SketchCow I want assholes shoving pull requests all day
02:40 🔗 SketchCow bai: Here's a question - are .webm files all that are needed with emularity
02:40 🔗 SketchCow Is there a second thingy
02:40 🔗 Vito` db48x: well, pitfall doesn't work in phantomjs either
02:41 🔗 Vito` doesn't throw errors, just fails to download the .json file
02:41 🔗 bai SketchCow: you mean .wasm?
02:41 🔗 SketchCow Yes
02:41 🔗 bai there's a .wasm and a .js file
02:41 🔗 bai when you build for wasm, the build system creates dosbox.wasm and dosbox.js - I rename that to dosbox.wasm.js
02:42 🔗 bai that way I can also have dosbox.js compiled with the old asm.js method
02:42 🔗 SketchCow Did you compile some of the new ones yet?
02:42 🔗 db48x Vito`: how does it fail?
02:42 🔗 SketchCow (My firefox dies like a dog when I go near it right now)
02:43 🔗 bai oh, no my laptop was getting too hot to hold so I shut everything down
02:43 🔗 bai I updates video drivers and I think it reset all my power settings
02:43 🔗 bai updated*
03:01 🔗 db48x https://github.com/ArchiveTeam/glowing-computing-machine
03:02 🔗 db48x Vito`: I guess we need to talk to folk at IA about it. Tracey or... um... whathisname... Hank?
03:02 🔗 SketchCow Or Sam
03:02 🔗 SketchCow Sam's fun to talk to
03:02 🔗 SketchCow He likes weird
03:03 🔗 db48x I couldn't think of a name, so: https://github.com/ArchiveTeam/glowing-computing-machine
03:03 🔗 SketchCow I liked the name
03:03 🔗 db48x oh, heh. I already pasted it :)
03:04 🔗 db48x needs some ssh keys, preferably ed25519, a list of apt packages, etc
03:05 🔗 db48x Vito`: and yes, making an AMI out of the machine once it works is the way to go
03:05 🔗 SketchCow Great
03:05 🔗 SketchCow I bet bai can list some required packages
03:06 🔗 SketchCow If we have some additional fuckery, like maybe a script that says "update to beta" or off-book stuff that makes the machine weird but can do some tests, that can sit to the side
03:12 🔗 bai if it's going to be run in a debian-based system, the magic command is apt-get build-dep mame dosbox
03:13 🔗 bai from there it all has to be build from github repos, emscripten has an sdk which makes it somewhat easier to script
03:14 🔗 bai basically the steps are 1) install all the build dependencies 2) pull down emsdk_portable.tar.gz, extract 3) run 'emsdk install sdk-incoming-64bit'
03:15 🔗 bai then from there we pull down either the mame or dosbox repos, and build using their standard procedures
03:15 🔗 * db48x adds Apt.buildDep [ "mame" "dosbox" ]
03:30 🔗 db48x bai: do you have urls for those git repositories?
03:42 🔗 bai yeah, one sec
03:42 🔗 bai https://github.com/dreamlayers/em-dosbox/ https://github.com/mamedev/mame
03:45 🔗 db48x done
03:53 🔗 db48x bai: https://github.com/ArchiveTeam/glowing-computing-machine/commit/08fde26793961e99aeaaec8676e70c4b6a15b035
03:54 🔗 Vito` db48x: it just stops at 2017-03-12T16:20:14 [DEBUG] Network - Redirecting to "http://ia801906.us.archive.org/cors_get.php?path=%2F7%2Fitems%2Femularity_engine_v1%2Fa2600.json"
03:55 🔗 Vito` and then emularity says "failed to configure emulator"
03:56 🔗 bai db48x: I think for em-dosbox you don't want master - he has it pinned to a different release
03:56 🔗 db48x bai: well, correct it then :)
03:56 🔗 bai em-dosbox-svn-sdl2
03:57 🔗 bai well I figure you have the files open already :D it looks good, the fun part will be seeing whether it runs
03:58 🔗 db48x indeed
03:58 🔗 db48x I'll have to run it tomorrow
03:59 🔗 db48x don't forget to add your ssh key
04:04 🔗 phe has quit IRC (Quit: Leaving)
04:24 🔗 bwn has joined #jsmess
04:46 🔗 SketchCow Should I write a new Readme.MD part?
04:47 🔗 SketchCow https://www.google.com/search?q=glowing-computing-machine also seems to be used elsewhere
04:49 🔗 SketchCow Probably want to move to another name
12:55 🔗 phe has joined #jsmess
14:03 🔗 tobbez has joined #jsmess
16:36 🔗 X-Scale has quit IRC (Ping timeout: 240 seconds)
17:00 🔗 X-Scale has joined #jsmess
22:46 🔗 bwn has quit IRC (Read error: Operation timed out)
22:54 🔗 bwn has joined #jsmess
23:05 🔗 phe has quit IRC (Quit: Leaving)
23:06 🔗 bwn has quit IRC (Ping timeout: 244 seconds)
23:14 🔗 bwn has joined #jsmess
irclogger-viewer