Install failure on windows 10 about calm

[simmihugs]

So it seems it was like you did expect - some other SDL2 in the path.

Though - its SDL2.dll not SDL2_image.dll causing this, but the error in the terminal hints at *_image
maybe this could be improved in the debug outpug

[simmihugs]

Little follow up - when double clicking the calm.exe
Windows shows an error (see screenshot) - maybe SDL2_image is out-to-date?

[VitoVan]

Thank you for trying this, I'm looking into it.

[VitoVan]

Just tested on:

OS Name	Microsoft Windows 10 Pro
Version	10.0.19045 Build 19045

with an expected result:

Now I'm trying to upgrade this OS, to see if it fails on the newer version Windows 10.

[VitoVan]

Another test, same OS, but upgraded:

OS Name	Microsoft Windows 10 Pro
Version	10.0.19045 Build 19045

[VitoVan]

Now, I have a wild guess, do you have a newer version of SDL2 inside your PATH?

By default, when we start CALM, it appends C:\calm\lib to the PATH env, like this:

PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\calm;C:\Users\vito\AppData\Local\Microsoft\WindowsApps;;C:\calm\lib

Maybe I should prepend this env rather than append.

I will work on this matter, and keep debugging. But in the meantime, if you would like to continue invest time on this, you could try removing the other potential SDL2 related path inside the PATH env.

Have fun, and sorry for this.

[simmihugs]

@VitoVan, it is definetly possible, that I have another version of sdl2 somewhere - I really should start using VMs when I try out stuff xd

I will look at my path variable tonight and let you know if I figure it out

[VitoVan]

Thank you for this, I'm considering to prepend the env to fix this.

And also, will see if I can do anything about the debug output, it seems to be out of my ability, but I'll try.

[simmihugs]

Thanks for the quick response BTW

As far as I'm concerned the issue can be closed

[VitoVan]

Thank you.

I'm considering to leave this open until CALM can be successfully started with the existence of other incompatible SDL2 in the PATH.

Thank you for firing up this issue instead of just throwing it away, I appreciated it a lot.