version

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

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

Rationale

bindbc-raylib3 uses semantic versioning as indicated in the dub guidelines. raylib does not use this procedure, so the version of bindbc-raylib3 cannot necessarily coincide with the version of raylib.

For example, version 4.2 of raylib eliminates some functions (breaking compatibility) although the major is not increased. bindbc-raylib3 instead increases the major according to the SemVer rules.

Clone and compile stable version of raylib

See compile raylib.

Clone and compile development version of raylib

Create a branch for desidered raylib version for example raylib version 4.0.0-17:

$ git checkout -b v4.0.0-17 3f595fda
$ git describe --tags
4.0.0-17-g3f595fda

and then compile raylib.

Available versions

bindbc version	note	raylib declared version	raylib git describe --tags
2.0.0		4.2.0	4.2.0-36-g234576da
1.0.0	Used in production	4.0.0	4.0.0
0.5.0	Static binding	4.0.0	4.0.0-17-g3f595fda
0.4.0	First raylib 4.0.0	4.0.0	3.7.0-567-g13376de0
0.1.0		3.7.0	3.7.0