[QUOTE=kriesel;513601]I've never used git; I always download a zipfile [...] [/QUOTE]
Ken, I updated the Makefile with the target gpuowl-win (changed the executable name accordingly, you'll get gpuowl-win, you need to rename it if the name is not good), added the strip too for the windows target.

If you don't have git, you need to put something manually in version.inc, changing this line:
echo "`git describe --long --dirty --always`" > version.inc
to something like:
echo "v6.5-8-g005297a" > version.inc

If you're building the version string manually, don't worry about the middle number, just replace it with 'x' such: v6.5-x-g005297a

The convention now is, if there are uncommited changes (local changes to the source), to suffix with -dirty: v6.5-x-g005297a-dirty , do indicate it's not exactly equal to that commit. (But for a public build it would be nice to be not-dirty, of course.)

You may try to install git, it may make the workflow a bit easier. After the initial "git clone" you'll only need "git pull" to get the delta.

[QUOTE=SELROC;513623]I don't know what it means, it seems that a string is missing,


echo "git describe --long --dirty" > version.inc
fatal: No names found, cannot describe anything.
echo Version: cat version.inc
Version: ""[/QUOTE]

Thanks! I didn't realize that the tag is not pushed by default to remote on "git push", fixed now. If you retry, the version should be properly set now. Also added a check which rejects an empty VERSION on compilation, to prevent non-intentional build without version.

So, "git describe" searches for a git tag where it takes the version string from (e.g. "v6.5"), and it didn't like that there was no tag at all, because I forgot to push the tag to remote.

[QUOTE=preda;513642]Thanks! I didn't realize that the tag is not pushed by default to remote on "git push", fixed now. If you retry, the version should be properly set now. Also added a check which rejects an empty VERSION on compilation, to prevent non-intentional build without version.

So, "git describe" searches for a git tag where it takes the version string from (e.g. "v6.5"), and it didn't like that there was no tag at all, because I forgot to push the tag to remote.[/QUOTE]


It has a git tag now, however it is not a version like x.y

[QUOTE=SELROC;513648]It has a git tag now, however it is not a version like x.y[/QUOTE]
It's just the commit hash which is all that's in version.inc. I'm prepending "6.5-x-" for now.


[QUOTE=kriesel;513606]Would need to first install git, yes? in the msys/mingw environment that's atop Windows 7, where the compiling gets done, I think. It looks like it's already there in msys2/mingw.

This gives 5 ways on windows, some oriented to Win 10.
[URL]https://www.jamessturtevant.com/posts/5-Ways-to-install-git-on-Windows/[/URL][/QUOTE]
If you already have it in mingw try that, otherwise I'd try the commandline bit of git for windows from your link.

[QUOTE=M344587487;513658]It's just the commit hash which is all that's in version.inc. I'm prepending "6.5-x-" for now.
[/QUOTE]


The commit hash is a precise way to specify a version, probably we need no more information for the purpose.

[QUOTE=SELROC;513648]It has a git tag now, however it is not a version like x.y[/QUOTE]
What do you mean, what is it like?

The version is supposed to look something like this:
v6.5-8-g005297a or v6.5-8-g005297a-dirty

Which gives at the same time a logical idea of the version (6.5), and access to the commit.

[QUOTE=M344587487;513658]It's just the commit hash which is all that's in version.inc. I'm prepending "6.5-x-" for now.
[/QUOTE]
It might have just the hash because you didn't pull the git tag ("v6.5") yet. Probably after the next git pull this will be solved.

[QUOTE=preda;513668]What do you mean, what is it like?

The version is supposed to look something like this:
v6.5-8-g005297a or v6.5-8-g005297a-dirty

Which gives at the same time a logical idea of the version (6.5), and access to the commit.[/QUOTE]




[url]https://github.com/preda/gpuowl/issues/43[/url]

[QUOTE=SELROC;513659]The commit hash is a precise way to specify a version, probably we need no more information for the purpose.[/QUOTE]
It is but not human-readable. The format preda is using is x.y-z-hash, might as well follow convention.

[QUOTE=preda;513669]It might have just the hash because you didn't pull the git tag ("v6.5") yet. Probably after the next git pull this will be solved.[/QUOTE]That did it. I was on the latest commit and either pulled before you added the tag or "git pull origin master" doesn't get the tag.

[QUOTE=M344587487;513674]It is but not human-readable. The format preda is using is x.y-z-hash, might as well follow convention.

That did it. I was on the latest commit and either pulled before you added the tag or "git pull origin master" doesn't get the tag.[/QUOTE]


exact, only "git pull" gets the tag.

Warning for ROCm users: refrain from upgrading to recently-released ROCm 2.3, there is a 5% perf degradation. [url]https://github.com/RadeonOpenCompute/ROCm/issues/766[/url]