rofl0r
nice PR, this makes the program usable in 2023 :thumbsup:
thanks! i've never heard that you're supposed to look at the actual pixel format of the SDL display surfaces. do you know of any resources documenting this?
ouch. having to call a function for every pixel sounds like performance's gonna take a major hit.
i guess you should ask @arsv, i copied most to the encryption code from his wsupp program...
yeah, i have the same issue when i use the SDL backend. it looks like its some bug in SDL 1.x which is triggered when several threads are active. IIRC...
meanwhile i developed a patch to fix this issue, see https://github.com/sabotage-linux/sabotage/commit/261c52650c033e82ea088a21df67ba0716ed3b62 since SDL 1.2 development has officially been halted, there's little chance this will ever make it upstream though. related:...
this unbreaks CI, so i guess it should be merged. though usually one uses `__APPLE__`, not `__MACH__` to check for mac os. @rogerman what do you suggest ?
implicit function declarations are nasty because they promote all arguments to int. on 64bit archs that leads to silent pointer truncation to 32bits with sign extension and subsequently crashes when...
> Ummm.... what?!! Who's compiling using implicit function declarations? basically anyone with a C compiler < gcc 14 who didn't stuff -Werror=implicit-function-declaration into his CFLAGS. the reason an implicit function...
> Yes, not including that flags for your build is the user's fault, and it should be considered a user error if the build fails. not including the flag leads...