Taeer Bar-Yam

Thanks for letting me know. From skimming the search results, this looks like this might be an issue with an old version of `SDL2`, and a new version of Windows...

[MAR1D.zip](https://github.com/Radvendii/MAR1D/files/10219923/MAR1D.zip) This won't work 100%, but can you let me know if this gets you to the main menu at least? That way I'll know I'm on the right track.

> but simply not importing the problematic header is a possible solution. You can import the problematic header *and* redefine the problematic functions, right? > You'll just have to carefully...

I haven't tested it yet, but this PR claims to fix the issue: https://github.com/NixOS/nixpkgs/pull/132937 Should we close this?

I'm also having this problem. Did you find a solution / workaround?

Ah, bummer. I'm not sure what the use-case for `--clear-symbol-version` is that works, given that it's also not documented in the man page (#258). But anyways, I'm exploring other options...

Oh it might have worked for your use-case, if you just wanted a particular binary to work on a particular computer. But it's not very robust; if there's a breaking...

I'm concerned by any solution that doesn't put an emitted header in a directory all on its own. That includes what's currently going on, but also what you seem to...

Thanks for the recatogrization, I wasn't sure if it was a bug or proposal. I don't know how the tags work, so maybe this is correct anyways, but I didn't...

I've uncovered even weirder behaviour. In `stdbool.h`, we have `bool` defined by `#define bool _Bool`, so I figured if I overrode this by putting ``` @cInclude("stdbool.h"); @cUndef("bool"); @cDefine("bool", "int"); ```...