-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Clarification request/Improvement] Add version and github info always, also when --enable-debug was missing #723
Comments
Yes. I agree, adding version info with github commit hash in non-debug builds will be very helpful. An earlier request - #581 (comment) |
Needs change in Line 140 in fd0683f
|
I am against to show GIT_REV in release mode:
|
@zdenop Where exactly is your problem to print the GIT_REV when users use --version ? I *have a problem when, as an expert, I run always the latest version, but sometimes after git pull the latest build is not the "installed" build. As a user I want to have the fastest code, i.e. built without --enable-debug. I again request to think over it, and to always - if available - burn the GIT_REV into the code. I ask you for this. |
Not using |
@zdenop, what about using GIT_REV only for versions without tag, no matter whether it is a debug or a release build? Then released stable versions would not show GIT_REV. |
Only ~6%? With LSTM mode? |
BTW, maybe we should add another debug/optimization option with |
This has now been implemented by recent commits by @stweil .
Please check with latest code from master and close the issue. |
I tried to build the new master version but
relevant lines are:
|
How are you trying to build? I used the following today, without any problem. #!/bin/bash |
|
@stweil Please see make error above. |
@Wikinaut, it looks like you are using git, but your latest tag does not match the expectations (MAJOR.MINOR.PATCH with MAJOR, MINOR and PATCH being numerical values, maybe followed by additional non-numeric characters). The latest tag should be |
I just built the master branch, as usual. git describe --abbrev=4 |
@stweil have a look (I just updated this above) to the make output libtool: link: ( cd ".libs" && rm -f "libtesseract_api.la" && ln -s "../libtesseract_api.la" "libtesseract_api.la" ) Especially to |
@Wikinaut, your local git has the latest code, but not the latest tags (see list of all tags). It still uses the old tag |
The error message which you see comes from |
What info do u see for |
|
and then
|
|
ok, works now. Result as wanted:
Closing this as solved, thanks. |
@stweil, according to the semver 2.0.0 spec, there should be only one BTW, from where the field before the commit hash comes from? |
I think that is number of commits since last tag, beta.1
…On Thu 29 Mar, 2018, 12:04 AM Amit D., ***@***.***> wrote:
tesseract 4.0.0-beta.1-59-g2cc4
@stweil <https://github.com/stweil>, according to the semver 2.0.0 spec,
there should be only one -. The rest should be replaced by dots.
BTW, from where the field before the commit hash comes from?
(59 here)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#723 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE2_o0bZI9uMx1qCMxYsmdDjOPypNc7sks5ti9fDgaJpZM4MDsWM>
.
|
As @Shreeshrii already said, 59 is the number of commits since the last tagged version. The 'g' before the hash might stand for 'git'. |
I know, that
tesseract --version
outputs the exact version and github commit hash, if it was compiled with./configure --enable-debug
, example:I wonder, why this is not output, when the configuration setting was not given and I suggest to modify the build code so that the version and github commit hash is always shown with the
--version
command.The text was updated successfully, but these errors were encountered: