[build] Make raylib available in package managers

[a3f]

This would ease deployment quite a bit for users. The package should install a tagged release (e.g.
1.9.4-dev).
If a more up-to-date or development snapshot can be requested, it should download the tarball for the newest master branch commit.
See Homebrew/homebrew-core@7f7b4bc for an example.

macOS

• Homebrew
• MacPorts?

Windows

• Chocolatey

Linux

• openSUSE
• Arch User Repositories (AUR)
• Linuxbrew
• Gentoo
• Your Linux distro's package repositories

BSD

• FreeBSD
• Your BSD's ports tree?

If you are able and willing to help, please tell.

[raysan5]

That would be a great addition!

Maybe @jubalh and @Martinfx could help on any of those?

[jubalh]

@a3f well, openSUSE has raylib in its official repository for quite some time already.

Edit: See https://github.com/raysan5/raylib/wiki/Install-on-GNU-Linux

OBS can also built Arch Linux, Debian, Fedora... packages if people are interested.

[a3f]

Good to know, amended the list. I should indeed have checked the Wiki first…

[raysan5]

Hi @Martinfx, sorry, my bad, I'm in the process of adding GLFW3 library as an additional raylib module (rglfw) and not uploaded the Makefile yet, I'm uploading it in the following days...

[Martinfx]

Hi @raysan5 i need maybe for port source code with freebsd patches (higher release ?) Thank you M.

[raysan5]

Sorry @Martinfx, I was also waiting for mini_al integration (replacing OpenAL Soft) and Makefile needs several changes... in the meantime just uploaded rglfw change in commit 9a75246

[jubalh]

BTW: the meson build files use library versioning.
I am not sure if the makefiles or cmake files do this too.
But it is essential to have this if you want to be included in Linux distributions. For this reason openSUSE uses the meson build files in raylib. However it seems that the cmake files added later look very good and cover more, right? If those also use library versioning it might be worth using those and removing meson.

Its also important to increase the major version number of the library version upon every ABI incompatible release (no need to increase general raylib major version just shared object major version number).

[OvermindDL1]

I am not sure if the makefiles or cmake files do this too.

Optionally yes, to both.

[jubalh]

@OvermindDL1 why do we do this only optionally so far? Can you point me to the lines?

[OvermindDL1]

Raylib itself doesn't yet, but a PR could fix that, it's a couple lines added in both the Makefile and the CMakefile.txt.

[jubalh]

So with optionally you meant 'it is in theory possible', now I get it. Well, I am aware of that ;)

In any case, if several Linux distributions package raylib, and each uses a different build system, and some has features others don't that might not be an ideal case.

@OvermindDL1 if you know how to do it for CMake it would be nice to do it there, I would switch the openSUSE package to use CMake then instead of meson.

I am afraid that upon version changes it is more easy to forgot to increase the so nr if you have 10 places to do it.

[OvermindDL1]

@jubalh In https://github.com/raysan5/raylib/blob/master/src/CMakeLists.txt you'd want to add a new line of something like (I see that things like raylib_VERSION_MAJOR and raylib_VERSION_MINOR exist, no PATCH interestingly, but are unused, so what is going on there? I'll use them, but usually you'd pull it from a VERSION file or something):

set_target_properties(${RAYLIB} PROPERTIES
  SOVERSION "${raylib_VERSION_MAJOR}.${raylib_VERSION_MINOR}"
)

Then when the INSTALL build command is run then it will output the library with full version information in the linux standard way on linux along with symlinks to one with just the major and minor version, one to just the major version, and one to the name itself (on windows it will not do this, but it will bake the version number into the file metadata so windows tools can introspect it and so forth on each platform).

You would of course generally use a VERSION file with a full semver and just read it in normally though, be sure to change the right numbers as the API changes over time.