Am Montag, 24. September 2012 10:04:43 UTC+2 schrieb James Le Cuirot:
Leptonica and its dependencies should build just fine for 64-bit
Windows, at least when using MinGW, because I fixed it some time ago.
Following that, I think Tom Powers ensured it also worked for MSVC.
I don't know about Tesseract itself. Try it and see. :)
On Mon, Sep 24, 2012 at 12:57 AM, troplin <tro...@gmail.com> wrote:
> since the installer for Windows will contain the libtesseract DLL in the
> next version (v 3.02), I'd suggest to build and distribute it also for
> 64-Bit machines.
> This would require to build all dependencies (leptonica, zlib, jpeg, gif
> etc.) for 64-Bit too, which is why I didn't try it so far.
>
My personal take on this is why go to all the bother? 32-bit apps work
fine on 64 bit Windows. Are people really crying for it? I doubt if
anyone really needs it to do OCR. The trend (based on the questions on
the main tesseract-ocr group) is people wanting to run on LESS
powerful hardware (like IOS or Android).
On my own Windows 7 64bit system that I built about 6 months ago
(admittedly a tiny sample):
64 folders in C:\Program Files\ which is where 64bit apps get
installed (over half of which look to be made by Microsoft)
127 folders in C:\Program Files (x86) (about a quarter made by Microsoft).
Taking a quick glance at the 64-bit apps, I honestly don't see any
that really *need* to be 64-bit. Having a 64bit OS is nice. You get to
use all that memory to run lots of big apps at the same time. In
particular it's nice when you are running say Ubuntu as a virtual
machine. 64bit apps? not so much. IMO, if people want to get higher
performance OCR they should try multiprocessing instead.
Whenever the next version of leptonica comes out, I currently have no
plans on providing 64bit DLLs (mainly because I don't relish the
hassle of building all the prerequisite image libraries). I already
have to build and test 4 configurations (over and over and over again
during the release process). Until someone demonstrates to me that
there is a strong, reasonable demand, I'm not going to volunteer to
double that amount.
--
You received this message because you are subscribed to the Google Groups "tesseract-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Sorry I don't have access to visual studio 2008.
You received this message because you are subscribed to a topic in the Google Groups "tesseract-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tesseract-dev/WhKDNnWRJ5Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tesseract-de...@googlegroups.com.
To post to this group, send email to tesser...@googlegroups.com.
Visit this group at http://groups.google.com/group/tesseract-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-dev/2058c208-8922-4ced-92df-b186f53627fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Any chances that you could provide vs2008+64bit. To build 64bit python-tesseract, I need vs2008 64bit built of libtesseract302.lib.
Thanks for the offer however I think ill keep to vs 2013 so I can compile the libs.
--
You received this message because you are subscribed to a topic in the Google Groups "tesseract-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tesseract-dev/WhKDNnWRJ5Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tesseract-de...@googlegroups.com.
To post to this group, send email to tesser...@googlegroups.com.
Visit this group at http://groups.google.com/group/tesseract-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-dev/d5dfae25-a089-4246-b709-f33a7a278355%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.