yes - for cygwin/msys should work:
 ./configure --enable-debug

to see gir revision number git should be in path, so configure can call
it...

Zdenko

On Thu, Jul 23, 2015 at 9:55 PM, Simon Eigeldinger <[email protected]
> wrote:

> hi,
>
> thanks for the info.
> so i guess then i might recompile my windows builds in debug mode then?
>
> greetings,
> simon
>
> Am 23.07.2015 um 21:11 schrieb zdenko podobny:
>
>>     1. Well if someone compile code from git (s)he should know what
>> revision
>>     is using ;-) And of course git code (unreleased) should not be
>> distributed.
>>     2. Current git code (should) shows version number 3.05.00dev
>>     or 3.04.01dev based on (main) branches. And once again compiled
>> program
>>     based on this code should not be distributed... It it for developers
>> for
>>     testing, probably it could be broken or even it could not work.
>>     3. If someone for any reason really need to see tesseract git revision
>>
>>     number (s)he should use debug mode (and not release mode). IMO if
>> anybody
>>     use git code I expect that (s)he use debug mode by default because
>> (s)he is
>>     testing and debugging code.
>>
>>
>>
>> Zdenko
>>
>> On Thu, Jul 23, 2015 at 6:33 PM, Simon Eigeldinger <
>> [email protected]
>>
>>> wrote:
>>>
>>
>>  Hi all,
>>>
>>> at the moment when you compile the versions from git you get the version
>>> number 3.04.00 when you do a tesseract -v.
>>> but i guess when you compile directly from git it should show the version
>>> number like in the autogen and configure scripts.
>>> because those also display the git hash.
>>> what do you think about this?
>>> so everyone using the program  where the version number shows up will see
>>> its a git compiled version.
>>>
>>> greetings,
>>> simon
>>>
>>>
>>>
>>> --
>>> Simon Eigeldinger
>>> Follow me on Twitter: http://www.twitter.com/domasofan/
>>> E-Mail: [email protected]
>>> MSN: [email protected]
>>> ICQ: 121823966
>>> Jabber: [email protected]
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "tesseract-ocr" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/tesseract-ocr.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tesseract-ocr/55B11765.7000905%40vol.at
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>
> --
> Simon Eigeldinger
> Follow me on Twitter: http://www.twitter.com/domasofan/
> E-Mail: [email protected]
> MSN: [email protected]
> ICQ: 121823966
> Jabber: [email protected]
>
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> https://www.avast.com/antivirus
>
> --
> You received this message because you are subscribed to the Google Groups
> "tesseract-ocr" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/tesseract-ocr.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tesseract-ocr/55B1469A.5030806%40vol.at.
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tesseract-ocr.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/CAJbzG8zV%2Bz5SGEeOgo9LywtWA7SohqQvxEbeatW0WQxUh77uWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to