use different version

raylib evolves rapidly and Ramon often releases new untagged versions (development versions).

bindbc-raylib can use either stable versions (eg 3.0.0) or development versions. Obviously it is necessary clone and compile correct version of raylib.

Convention

We will use different branches for different versions of raylib. Branches related to a tagged versions have the same tag name with prefix v (eg. v2.6.0, v3.0.0), branches related to development versions have name derived form git hash code with prefix g.

For example, to use the development version 72443f8f, we create the g72443f8f tag:

$ git checkout -b g72443f8f  72443f8f

Now we are on branch g72443f8f.

The D version derives from git describe, so:

$ git describe --tags
3.0.0-70-g72443f8f

has D version RAYLIB_300_70.

Set version on dub file

raylib versions can be configured by adding appropriate versions directive in your dub file.

The following table lists each identifier and the raylib versions they enable:

raylib version	raylib commit	Version ID
2.5.0		Default
2.6.0	117696a8	RAYLIB_260
3.0.0	7ef114d1	RAYLIB_300
3.0.0-70-g72443f8f	72443f8f	RAYLIB_300_70

For examples, in order to use raylib version 2.6.0:

dub.json

"versions": [ "RAYLIB_260" ],

dub.sdl

versions "RAYLIB_260"