Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
PhysFS_init now returns 0 in 5.2.5 #1029
Hi, I just recently upgraded my Allegro project from 5.2.4 to 5.2.5.
I cannot get PhysFS to initialise. Before it worked just fine but now it will return 0, the error code for unsuccessfully initialising, without including any error code in getLastError or getLastErrorCode.
I'm developing on Windows 10 64-bit and downloaded Allegro through nuget.
I was able to workaround this problem by replacing my physfs.lib and physfs.h with the version from 5.2.4.
So the difference between the two Nuget packages is that we upgraded PhysFS from 2.0.3 to 3.0.1.
It looks like this is the issue described here: https://icculus.org/pipermail/physfs/2018-October/001274.html.
What I'll do is patch in the fix here (https://hg.icculus.org/icculus/physfs/rev/ece6769c0676) and push out a new version of the deps + allegro.
Thanks for reporting this!
Actually, it appears to be something that affects at least WinXP, but only if you build with an older Visual Studio...it's a mystery. I released PhysicsFS 3.0.2 today with something that works with both win32 behaviors: https://icculus.org/pipermail/physfs/2019-March/001280.html