,
15 tweets,
2 min read
Read on Twitter
it's cool trying to do *anything with someone elses C project at all* because the solutions to all the problems you get compiling are "simple": just edit the compiler/linker commands. which is impossible because I do not, and cannot, understand automake
"just add -no-static-link-xyzzy-metroid=HINGUS to your gcc" that's a *great* idea for my "babbys first hello world" but how the fuck do you expect me to make that happen with a 15 year old emulator project
"just edit the makefile" there are fucking dozens in every project and none of them seem to do anything. i can edit file after file after file and nothing changes
and of course it's not exactly the stackexchange etc peoples fault in that the actual answer is "give up" or "we can't help you, sorry." this is the kind of problem you can't tell someone else how to fix because the surface area is too big.
you either know or you don't know, and if you know then you know how to figure it out, not how to do it. because it always shifts and changes and nothing stays in the same place
anyway who the fuck can tell me why this exe i just compiled with mingw wants libgcc_s_dw2-1.dll but when i put the one from mingw's bin in the folder it complains about a missing entry point in the file i just fucking compiled the exe against
dlls are the dumbest shit
love too be stopped before i can start on every single computer thing i try to do as a hobby to distract myself from the permanent unending feeling of impending doom because everything begins with 14 hours of yak shaving
and you can never tell how far you are from done shaving the yak. is the answer right around the corner or are you in completely the wrong place? what's the right path to follow, spending an hour trying to figure out how to static link, or compiling a new DLL?
the yak could be the size of a house or the size of a cat, and you don't know until you're done shaving it, and when you're done shaving it you never really feel like you got all the fur off
the difficulty in programming is never programming itself, it's always that the tools are so dogshit-stupid they can't solve any problem on their own, provide any assistance or give a meaningful message
and no, I don't feel i need a CS degree to assert (ha) that compilers et al could be much, much, much smarter than gcc and fucking autotools
make clean; make. now waiting to see if my -static-libgcc flag will be noticed and fix this issue. meanwhile my thoughts about how to implement the thing i was doing are wasting away, eroding by the passage of time as i shave this yak instead of testing code changes
i could try changing the r_coefficient no you have to shave this yak. i could try overwriting the CGA16 CLUT no you have to shave this yak
welp, okay. I give up. I'm closing all the associated windows and tabs and never trying this again. If anyone has an idea how to fix the error I mentioned in this thread that'd be cool.
