Time |
Nickname |
Message |
00:39
🔗
|
|
azakai has quit IRC (Read error: Operation timed out) |
01:52
🔗
|
|
kripken__ has joined #jsmess |
02:25
🔗
|
|
kripken__ has quit IRC (Quit: Ex-Chat) |
02:25
🔗
|
|
kripken_ has joined #jsmess |
09:20
🔗
|
|
datajerk_ has joined #jsmess |
09:21
🔗
|
|
datajerk has quit IRC (Read error: Operation timed out) |
14:59
🔗
|
|
kripken_ has quit IRC (Ping timeout: 255 seconds) |
16:40
🔗
|
|
azakai has joined #jsmess |
16:48
🔗
|
|
azakai has quit IRC (Remote host closed the connection) |
21:18
🔗
|
|
godane has quit IRC (Read error: Connection reset by peer) |
22:02
🔗
|
zino_ |
Emularity does single driver builds of Mame, right? If so, where can I find how it does that? |
22:02
🔗
|
zino_ |
I'm about to set up tests for single driver builds of regular Mame, and it would be nice if I don't have to go through and fix dependencies from scratch for drivers that need extra SOURCES=. |
22:20
🔗
|
SketchCow |
MAME itself does single driver builds |
22:20
🔗
|
SketchCow |
We just utilitze that |