tobil4sk

When running on lua 5.1, the issue is particularly bad because it is not even possible to run `luarocks install compat53` successfully: ``` D:\a\lua-simdjson\lua-simdjson\lua_install\bin\lua.exe: ...n\lua_install\luarocks\lua\luarocks\core\persist.lua:25: bad argument #1 to 'load'...

@hishamhm Thanks for the detailed explanation! > To avoid the chicken-and-egg problem of LuaRocks having dependencies on those Lua/C libraries, we should just vendor them in. It's not a very...

This issue is somewhat related: #249. Right now, dev libraries are handled the same for both `-lib name:1.2.0` in hxml or `{"name" : "1.2.0"}` in haxelib.json. So, what would need...

You can test this out more easily by running `haxelib path something_else something`, with the library names in the order they appear in the hxml. This way you can confirm...

I think some of these concerns will be resolved once a better library resolution system arrives, which will allow locking library versions within a project so it is clear which...

Also should be investigated whether it is still necessary to set `_WIN32_WINNT`

The unnecessary `WINSOCK_API_LINKAGE` seems to have been copied and pasted from the previous code, where the loading relied on `WINSOCK_API_LINKAGE` rather than `GetProcAddress` as it does now: https://github.com/HaxeFoundation/hxcpp/commit/b08a79d119d8646c10f713010a8b2d82f2a31690 Here is...

In that case, perhaps my problem is the fact that switching VT is causing the boot logs to flicker on the screen? Which would be unrelated to sddm.

What does it show if you run `haxelib list`? and could you manually navigate to `C:\HaxeToolkit\haxe\lib\flixel` and see what that folder contains?

Is it not possible to perform a more generic check for ansi color support? It's possible that these CI environments will change, or that not all environments are covered.