New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report Git Version in Csound's output #676
Comments
For what it’s worth, I think reporting the Git commit hash with Csound’s version is a very good idea! |
I've done this now. Can you check whether it's the best format and we can close this ticket? |
this will break ccache on every git pull. It would be great to have it defined only for Also, this should probably only be used when BUILD_RELEASE is not defined. |
Probably minor, but this also affects builds done in a git repository not linked to this one (like the debian downstream one), and thus the hashes reported will be highly misleading |
csound.c only now. I've commented out the musmon.c duplicate as it is only confusing things. |
if everyone's happy with this now, I will close the ticket. |
I think I have it working now for Windows. CMake needed to use the windows @vlazzarini could you test to make sure this works on OSX? If so, then I'm On Fri, Oct 21, 2016 at 11:14 AM, Steven Yi stevenyi@gmail.com wrote:
|
I get this output with the latest from git: $ csound --help At first I didn't understand what the [] was. It'd be nice if that was On Thu, Oct 20, 2016 at 5:55 PM, Felipe Sateler notifications@github.com
|
The latest isn't working for me here on Windows. Investigating now, will On Fri, Oct 21, 2016 at 5:02 AM, vlazzarini notifications@github.com
|
Strange... the code should at least print [commit: ] |
working on OSX
|
FWIW, it should print [commit: none] when no hash could be found. On 25 October 2016 at 15:23, vlazzarini notifications@github.com wrote:
Saludos, |
Reporting the git version used to compile the application would help developers when users report problems. The information could contain the git commit hash or use git describe (for example, something like "git describe --abbrev=4 --dirty --always --tags"). We would need to figure out:
For the last point, we currently show information such as:
Csound version 6.07 (double samples) Jul 2 2016
We could have something like:
Csound version 6.07 (double samples) Jul 2 2016 [4904caa6f8ad688c59ae3703d2825162e0fa6a1a]
or using the same abbreviated commit hash as shown when using "git log --abbrev-commit", we could have something like:
Csound version 6.07 (double samples) Jul 2 2016 [commit: 4904caa]
The text was updated successfully, but these errors were encountered: