[02:30] *** datajerk has joined #jsmess
[04:16] *** balrog has quit IRC (Read error: Operation timed out)
[04:19] *** balrog has joined #jsmess
[05:23] <DFJustin> the output of `mame -listxml` specifies which drivers are marked as working
[05:26] <DFJustin> under <driver status="good"
[06:06] <SketchCow> OK, so. ideally I do a make on the SISYPHUS system
[06:22] <SketchCow> Obviously, this is taking some effort.
[07:17] *** Sgeo has quit IRC (Read error: Connection reset by peer)
[08:16] *** tech234a has quit IRC ()
[08:23] *** tech234a has joined #jsmess
[14:19] *** Sgeo has joined #jsmess
[14:54] <SketchCow> Finally getting this to compile in the ubuntu machine is intense!
[15:15] <SketchCow> 0.231 is taking so long to compile I see 0.232 came out in the meantime.
[15:32] <SketchCow> I'm compiling 0.232 in parallel on the box.
[17:08] <SketchCow> Wow, it takes a while to compile MAME, he noted dumbly
[17:53] <SketchCow> So, it JUST got pointed out to me that an XML of MAME is automatically generated each time.
[17:53] <SketchCow> https://github.com/mamedev/mame/releases/download/mame0232/mame0232lx.zip
[19:11] <bai> is the question "which new machines does this new build of MAME support?" or is it "...and which of them still work when compiled to WASM?"
[19:12] <bai> I guess there's always the manual verification crowdsourcing project whenever a new machine goes live anyway