[build] Use library versioning

[jubalh]

Hi,

How about using library versioning?

Would be great.

[raysan5]

Well, I decided to keep it simple and just increase version second number on every release.

At the beginning I tried to be more accurate with versioning but I noticed I was changing a lot of things (API and ABI) from version to version, most of the time versions are not compatible and I don't like to keep deprecated functions around. Just decided to do it that way.

But if you have some proposal to improve that and want to work on that, let me know, we can discuss it.

EDIT: Not sure if I understand clearly what you mean...

[jubalh]

Thanks for the quick response @raysan5.

I like raylib, and think it should be more widely available. For this reason I package it for the openSUSE Linux distribution. To make it easily installable for more people.

Anyways, currently you ship a .so and .h file.
Which means that only one version of the library can be installed in /usr/lib/ (for example). Library versioning would produce file like raylib.so.1 etc. And a link in /usr/lib/raylib.so would link to such a version. Like this it would be possible to install multiple versions of a library on the same system.

Also with some tools we could detect when a ABI change occurs without a version bump of the library, which could lead to problems later on.

[raysan5]

Hi @jubalh, it sounds great to me to make raylib package available for openSUSE Linux distro!

I usually work on Windows OS so I focused raylib release and testing on that system but it would be great to make raylib more widely available to the Linux community, specially for education environments.

Any help on that direction is really welcomed! :)

[jubalh]

I think this issue can be closed as of #299