Automate kha_version define about khamake HOT 5 CLOSED

krab (with a small k like all the command line tools) just uses --depth 3 for all _bin repos, pretty simple. Starting with 2019 I plan to use yearly branches for the bin repos so regular clones are also getting faster. Also looked into git-lfs to speed things up but sadly it's horrible on github (but could just use bitbucket for the bin repos) and hard to install on macOS.
But, yes, not too happy about people using kha_version defines anyways but not sure about just getting rid of it either.

from khamake.

But commits in git do not have a well defined order, a >= isn't really possible. I think the best solution would be a bot that adds a version commit once per month.

from khamake.

Yes the commit_xyz thing was a just silly example. Even a monthly auto-update would be great.

from khamake.

Thinking about this more, it could indeed cause more trouble than worth in the end. Maybe getting rid of the define would force us into a more robust solutions.

For me it started with Kha being slow to clone (armory needs fast update mechanism) but using Krab as a basis it now seems I will be able to just make it clone fast enough.

from khamake.

The fastest way I found so far, if you only need shallow copy to start with:
git clone --recursive https://github.com/Kode/Kha --depth 1 --shallow-submodules --jobs 4

This finishes in ~80 seconds for me, of which haxe_bin takes up to 40 seconds. Once haxe3 is out it could maybe fit into 1 minute which is reasonable.

from khamake.