[00:57] I'm home! [00:58] 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] I was thinking we could br real ambassadors for it [00:59] no, I think that's great [00:59] instead of the emulator logo? [00:59] I don't want to do it unless all of you sign off, since you put work in [00:59] I would say in addition [00:59] Either way. [01:00] Either an additional splash before running, or changing the loading screen [01:00] I just mean the idea right now, not the implementation [01:00] 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] That leaves db48x [01:02] Also, did we have an opinion to shared aws instance [01:02] Documented and scripted so we can turn one into a box if we need several [01:03] aws is fine, just remember when allocating the disk space that you'll probably need a good size [01:03] and probably not the lowest-end of IO performance [01:03] if you do it you can close this issue: https://github.com/jsmess/jsmess/issues/97 [01:03] I had a 15gb virtual drive set up for my vm and it wasn't enough, clang was taking 14gb by itself [01:04] Poor yoz, he got so busy [01:04] Yeah, we'll do this one [01:04] 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] the thing you do want is multiple cores [01:05] 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] (within the hour) [01:07] 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] but it should be simple to just spin it up, compile, and shut down [01:10] Playing Windows 3.1 [01:10] Can you compile a couple of the others in the WASM set on metacade? I'd like to see the speed. [01:11] ok, yeah I'l redo builds for all of them [01:17] Tell me how this sounds as a general plan for the builds. [01:18] I will make an amazon instance, and write a script, which then adds the needed components for a build system. [01:18] Then we do rounds of error checking, etc. [02:23] Vito`: example_ia.html works for me [02:23] Vito`: https://github.com/db48x/emularity/blob/master/example_ia.html [02:23] SketchCow: WebAssembly logo will be nice [02:24] Great [02:24] Unanimous [02:24] db48x: example_ia doesn't work for me with those two other objects [02:25] https://github.com/carlosbaraza/web-assembly-logo [02:25] db48x: and example_ia doesn't work for me in phantomjs with the object it specifies by default [02:26] Vito`: I get a 503 from the server on Oregon Trail as well... [02:27] db48x: right, but it works fine going to the regular archive.org url for it [02:28] maybe cors.archive.org is borked [02:28] regular archive.org page doesn't use cors.archive.org [02:29] SketchCow: for a build machine we should use a proper configuration system like propellor, rather than writing our own system [02:31] Vito`: for now I suggest testing with Pitfall_Activision_1982 [02:31] not sure why it would fail on one but not the other though [02:32] You just outstripped my knowledge [02:32] :) [02:32] I'm always trying to take the load off people, but I can only work with my limited skills [02:32] I do everything with scripts [02:32] I'm willing to be team secretary [02:34] 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] 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] 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] repos* [02:34] I'm just saying I can't do it [02:35] But I'll fund AWS or other machinery [02:35] By the way, you all know I had a heart attack, right [02:36] (This is unrelated to a container setup) [02:36] 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] 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] eg, a script which uploads to IA [02:38] if you're on AWS, you shouldn't be using a build system, you should be making an image [02:38] should just be able to spin up an AMI that has everything set up already [02:38] 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] whatever it is, it's a set of packages and a couple short scripts [02:39] My specific interest is easy recreation by people outside our happy team [02:39] I want assholes shoving pull requests all day [02:40] bai: Here's a question - are .webm files all that are needed with emularity [02:40] Is there a second thingy [02:40] db48x: well, pitfall doesn't work in phantomjs either [02:41] doesn't throw errors, just fails to download the .json file [02:41] SketchCow: you mean .wasm? [02:41] Yes [02:41] there's a .wasm and a .js file [02:41] when you build for wasm, the build system creates dosbox.wasm and dosbox.js - I rename that to dosbox.wasm.js [02:42] that way I can also have dosbox.js compiled with the old asm.js method [02:42] Did you compile some of the new ones yet? [02:42] Vito`: how does it fail? [02:42] (My firefox dies like a dog when I go near it right now) [02:43] oh, no my laptop was getting too hot to hold so I shut everything down [02:43] I updates video drivers and I think it reset all my power settings [02:43] updated* [03:01] https://github.com/ArchiveTeam/glowing-computing-machine [03:02] Vito`: I guess we need to talk to folk at IA about it. Tracey or... um... whathisname... Hank? [03:02] Or Sam [03:02] Sam's fun to talk to [03:02] He likes weird [03:03] I couldn't think of a name, so: https://github.com/ArchiveTeam/glowing-computing-machine [03:03] I liked the name [03:03] oh, heh. I already pasted it :) [03:04] needs some ssh keys, preferably ed25519, a list of apt packages, etc [03:05] Vito`: and yes, making an AMI out of the machine once it works is the way to go [03:05] Great [03:05] I bet bai can list some required packages [03:06] 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] if it's going to be run in a debian-based system, the magic command is apt-get build-dep mame dosbox [03:13] from there it all has to be build from github repos, emscripten has an sdk which makes it somewhat easier to script [03:14] 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] 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] bai: do you have urls for those git repositories? [03:42] yeah, one sec [03:42] https://github.com/dreamlayers/em-dosbox/ https://github.com/mamedev/mame [03:45] done [03:53] bai: https://github.com/ArchiveTeam/glowing-computing-machine/commit/08fde26793961e99aeaaec8676e70c4b6a15b035 [03:54] 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] and then emularity says "failed to configure emulator" [03:56] db48x: I think for em-dosbox you don't want master - he has it pinned to a different release [03:56] bai: well, correct it then :) [03:56] em-dosbox-svn-sdl2 [03:57] well I figure you have the files open already :D it looks good, the fun part will be seeing whether it runs [03:58] indeed [03:58] I'll have to run it tomorrow [03:59] don't forget to add your ssh key [04:04] *** phe has quit IRC (Quit: Leaving) [04:24] *** bwn has joined #jsmess [04:46] Should I write a new Readme.MD part? [04:47] https://www.google.com/search?q=glowing-computing-machine also seems to be used elsewhere [04:49] 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