raylibVersion symbol not included in MSVC DLL for raylib 4.2.0

[schveiguy]

In raysan5/raylib#2671 it was noted that the MSVC dll for raylib 4.2.0 doesn't properly export the raylibVersion symbol.

The fix is simple. But there will not be a new binary built! So we can include the DLL directly on our repository. However, if we start going that route, we may as well just include them all. Or at least set up a way to download them all.

My first inclination is to include all the pre-packaged binaries on the repository, and then provide a sub-project to install it to the right place -- either your project directory (Windows) or /usr/local/lib (Posix). Then building can be done without having to properly install the lib files.

[EugZol]

Would be helpful if this was solved and binding actually worked :)

[schveiguy]

Sorry. I fear there is zero chance that Ray will fix the official build. The only thing I can do is either a) disable the validateRaylibBinding function in windows, or b) provide my own corrected build.

I will see if I can in the next week make a build on Windows. I don't have a Windows system that I use regularly, so it's a process...

[EugZol]

No worries, thanks for your work! I don't know much about C or D ecosystems and how things work traditionally but bundling dll in the bindings seems like a good idea to me.

[schveiguy]

Please try out the new raylib-d install script in 4.2.1 and see if it fixes your issue.

[schveiguy]

I'm satisfied this is fixed.