Our buildsystem expects version tags in the format v1.2.3-4-g00abcdef (tag + commit distance to tag + commit hash). However, since https://github.com/SFTtech/openage/pull/1576 we call git describe --tags. When HEAD is tagged, this command only outputs the tag and omits commit distance and commit hash (only v1.2.3 is returned). This results in a configure failure since our regex cannot match the version format in this case.
This PR switches the version fetch command to git describe --tags --long, so that the long format is always used.
Our buildsystem expects version tags in the format
v1.2.3-4-g00abcdef(tag + commit distance to tag + commit hash). However, since https://github.com/SFTtech/openage/pull/1576 we callgit describe --tags. WhenHEADis tagged, this command only outputs the tag and omits commit distance and commit hash (onlyv1.2.3is returned). This results in a configure failure since our regex cannot match the version format in this case.This PR switches the version fetch command to
git describe --tags --long, so that the long format is always used.