Closed vsiverson closed 12 years ago
This bug has been fixed by adding a "default version" string that will be updated with each tagged release to github). This default string will be presented by the --version option when executables are built without an underlying git repository to query for more specific version information at compile time. Because this is a low severity bug, this fix will be included in the next push to the repository that updates the version tag (i.e. v0.3.1).
If the SEAStAR tools (v0.3.0) are compiled from source that is not associated with (cloned from) a git repository, the --version parameter of all tools will fail to produce a usable version string. This can occur e.g. when the code is downloaded as a zip file or tarball rather than using a git clone command, or if the SEAStAR source directory is copied to a new location without the underlying git repo, and then recompiled.
This issue does not appear to impact use of the tools in any other way.