[00:03] I sent him one more thing, and then I'm going to ask for more help. [00:03] I have to go find where we defiined the request on twitter so I can make it again. [00:22] So disappointing/tiring [00:27] https://twitter.com/textfiles/status/936753442554634241 [00:34] bai: Multiple people coming in [00:34] I should do a write-up of the challenges or something [00:36] Yes please [00:40] Hi, hi, folks. [00:41] *** A_Scanner has joined #jsmess [00:41] Hello, [00:41] Somebody need a bit of help with c++ / javascript stuff? [00:42] Yep [00:42] bai can explain/provide a link [00:42] or 10 [00:42] bai: Maybe we should do a google doc? [00:42] We can just add the overview and the rest quickly [00:42] hacking parrrty [00:43] awesome. I was just heading out to the 26oo meet but I can postpone going for a bit. [00:44] nah if you're heading out, go for it - we should really organize some of these thoughts so we can share and collaborate better, explaining them on irc for each person who wants to have a crack at it gets rough :D [00:44] it's a tricky problem with a lot of run-up knowledge [00:44] Yeah, just idle here and we'll work on that doc. [00:44] bai: Should I start it or you [00:44] Google docs sound pretty good. [00:45] go ahead and start it and do the quick overview, and I'll fill in the details when I get a chance [00:46] I've got 12/ish years experience in programming and I like challenges. I learned with C++ but haven't dipped into it as much as I'd like. I'm good at gnarly problems tho/ [00:46] how's your JS? [00:46] so anyways, I'll idle and be back on later. I can get in real deep shit with JS. [00:46] this is one of those weird problems that spans both worlds [00:46] excellent [00:48] Sounds like a juicy problem. Looking forward to the write up. [00:48] bai: You're invited to edit [00:51] https://docs.google.com/document/d/1FHmn1kO3PGYYCRJejZsZMFk_BxWer_pOaTUANRFroM8/edit?usp=sharing [00:51] (That's the view version) [00:54] I'm quickly setting up a second machine for screenshotting. [01:03] More people coming [01:05] *** n00b110 has joined #jsmess [01:07] *** n00b110 has quit IRC (Client Quit) [01:12] *** testerpoo has joined #jsmess [01:17] *** testerpoo has quit IRC (Quit: Mutter: www.mutterirc.com) [01:18] And more still [01:57] *** testerpoo has joined #jsmess [02:02] *** ted______ has joined #jsmess [02:51] *** testerpoo has quit IRC (Quit: Mutter: www.mutterirc.com) [03:14] *** n00b211 has joined #jsmess [03:14] *** n00b211 has quit IRC (Client Quit) [03:27] Nobody talking though [04:22] bai: Any time to do it tonight or should it wait [04:46] I'm baaack.. [04:46] looking at the google doc [04:47] k. Is a good start. [04:49] So... stupid question what OS/platform and version do you you use for mame? IE.. what type of vm should I use to compile mame and is there a preferred branch/revision etc that I should use as source? [04:56] SketchCow: I'll fill in some stuff tonight, harass me if I don't :D [04:57] I take it http://www.mess.org/compiling_mess is up to date? I'll get that set up in the morning. [04:58] A_Scanner: I normally use a linux system to compile, ubuntu is my personal preference but whatever you're most familiar with, as long as it's new enough, should work [04:58] bai: cool. I'll just pop a vm up just for this to keep things neat and tidy. [04:59] the compile instructions for the web version are a bit different - those instructions are for building a native build [05:00] but you probably want to go through that process once first anyway just to make sure you get all the prerequisites to building [05:00] Ok cool. Is the web stuff documented someplace? [05:00] plus you need a native build to get information to build the stripped-down web builds, anyway [05:01] let me see if I can find official docs. we used to have a complicated custom build process, but now it's been built in to MAME's normal build process [05:02] right-O! Yay, checkpoint to make progress. I've got to get some sleep for a while but I'll work on this midmorning. [05:02] https://github.com/mamedev/mame/blob/1bcb694f8d7db37e03f07c080edcded5fb22f554/docs/source/initialsetup/compilingmame.rst#emscripten-javascript-and-html [05:21] DFJustin: https://archive.org/details/a8b_scat_217 - any idea why that dies [05:23] Ignore, it's some cookieish [05:29] Well, this has been a frustrating screenshot night [05:29] Getting the atari screenshotting to work, huge pain in the ass, no reason. [05:30] But sounds like we're getting some MAME work done, that's great [15:43] *** n00b335 has joined #jsmess [15:44] *** n00b335 has left [15:58] bai: When you get a chance, help with that doc - we have some good people who reached forward [15:58] A_Scanner: How goes it [18:17] *** n00b859 has joined #jsmess [18:19] *** n00b859 has quit IRC (Client Quit) [19:11] SketchCow: back online and going to build it all. [19:11] BUILD ALL THE THINGS! [19:38] *** Scanner_A has joined #jsmess [19:42] *** A_Scanner has quit IRC (Read error: Operation timed out) [19:51] *** A_Scanner has joined #jsmess [19:55] I'm just getting a new vm installed to use for this. I found out that virtual box and hypervisor-v really, really don't like each other. [19:56] *** Scanner_A has quit IRC (Read error: Operation timed out) [21:15] Been compiling for a while. of course needed a few packages to fully compile and as usual... it's an iterative process. I'm currently compiling mame itself.