This bug report was migrated from our old Bugzilla tracker.

Reported in version: 2.0.1
Reported for operating system, platform: Windows (XP), x86_64

Comments on the original bug report:

On 2013-12-25 17:29:02 +0000, wrote:

So... If you compile SDL2-2.0.1 on Windows XP (64bit) and run it on Windows XP (64bit), it works okay.

[Static compile, just to be sure -- haven't tested the dll output]

But if you run your static compiled SDL app which was built on Windows XP, on a non-XP system... It always return GL_VERSION 1.1.0... No special code - minimal testcase: Init SDL, Create window, Create context, Check GL_VERSION

Also, I think this might be true on only 'some' cards - specifically probably nvidia... but possibly others too.

I've run GLFW on those same systems and it gets proper GL version

On 2013-12-31 12:48:58 +0000, wrote:

And using the precompiled .a lib from libsdl.org works too... so i'm guessing it wasn't built on XP and there hasn't been proper testing with XP. :)

On 2018-08-06 21:20:22 +0000, Ryan C. Gordon wrote:

Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.