Originally created by: *anonymous
Originally created by: PhilEHol...@googlemail.com
I noticed this once when Graham was release meister - I've seen it twice since I took over. The current 2.17.16 executable correctly sets its version number when it commpiles a lilypond score, but right clicking the .exe and viewing the details tab report the version number as 2.17.15. It's obviously somethin off with GUB, but I've not investigated further at present.
Originally posted by: PhilEHol...@googlemail.com
I believe this is an artefact of GUB not rebuilding all files properly unless some clear up is done after the previous build. When I've not run
rm -rf target/*/*/*lilypond*
in the gub directory, I believe I have had the version problem. The most recent build (2.17.19) was built following the rm command, and has the correct version. When I have time I'll investigate further.
Diff: