Replacing the tesseract 3.02 alpha vs2008 directory
Tom Powers
in the SVN repository. (Aaargh! gmail won't accept my attachment ---
presumably because it has my tesshelper.py python script in it --- so
instead download tesseract-ocr-3.02-vs2008-2012-02-13.zip from this
link: http://www.mediafire.com/?xbk8hy32dy5b6fa)
Since it is mostly an updated and more complete version of my earlier
(and still not done) work for 3.01, the earlier discussion "Enhancing
the tesseract 3.01 Visual Studio 2008 distribution" [1] of the vs2008
Solution's design is worth reading.
See vs2008\doc\index.html for full documentation on how to use this new
Solution (the "Programming with libtesseract" section still needs work).
Digression:
It would be nice if we could directly serve these html pages from the
SVN repository (and then we could link to index.html from the Wiki). See
"How can I make SVN serve HTML and images with the correct
Content-Type?" [2] for details on how to correctly set up the mime types
for these files. "HOWTO: Publish Javadoc on Google Code" had a bit more
info on how to automatically do this when using TortoiseSVN, but that
page has since disappeared. You can still look at the cached version
[3].
vs2008\doc\versions.html lists the changes I've made relative to the
current SVN vs2008 directory.
zdenko: I moved mathfix.h from vs2008\include to vs2008\port. This is
more appropriate since I now envision the vs2008\include directory to be
only files that need to copied to the "public" include folder (used when
building 3rd party apps that won't be part of the tesseract-3.0x
tree). Maybe it should be renamed vs2008\public_include?
Everything built fine under Windows 7 64-bit and Visual Studio 2008 SP1
(assuming issue 614 [4] is resolved as I suggested there). Everything
also ran except that I noticed the new shapeclustering training app
crashes when I give it no arguments?
Any problems with the vs2008 solution (things won't build, or you can't
understand the docs) should be reported in this thread.
Problems with v3.02 itself should still be posted to the original alpha
announcement thread [5].
-- Tom
[1] http://groups.google.com/group/tesseract-dev/browse_thread/thread/75be5c97eb4d1b3c
[4] http://code.google.com/p/tesseract-ocr/issues/detail?id=614
[5] http://groups.google.com/group/tesseract-dev/browse_thread/thread/ef8c6819fc5385f
zdenko podobny
- tesseract_versionnumbers.vsprops (and leptonica_versionnumbers.vsprops) is placed in "vs2008\include", but projects expects it in "..\..\..\include\tesseract_versionnumbers.vsprops"...
- I changed 'class DLLSYM STRING' to 'class CCUTIL_API STRING' as local solution for http://code.google.com/p/tesseract-ocr/issues/detail?id=614:
- Configuration DLL_Debug created libtesseract302d.dll, tesseract-dlld.exe, but produced error for other project ( just errors see dll_debug.log).
- Configuration DLL_Release created libtesseract302.dll, tesseract-dll.exe, but produced error for other project ( just errors see dll_release.log).
- Configuration LIB_Debug finished without problem (Build: 11 succeeded, 0 failed, 0 up-to-date, 0 skipped)
- Configuration LIB_ Release finished without problem (Build: 11 succeeded, 0 failed, 0 up-to-date, 0 skipped)
- APItest solution do not have correct path for leptonica (should be '..\..\..\..\include\leptonica' is '..\..\include\leptonica' ) and tesseract (points to '..\..\include\tesseract', but there in no include\tesseract directory).
- idea behind 'port' and 'include' directories is that 'include' has files needed only for VC++ 2008 (they are problem for mingw) and 'port' has files needed for building on windows... This should be changed/improved because leptonica headers are include directory and there are needed also for mingw ;-) So you can changed it as suitable.
Tom Powers
> Tom,
>
> thanks for great contribution. I just tried it today (quickly) and here is
> quick response:
>
> tesseract_versionnumbers.vsprops (and leptonica_versionnumbers.vsprops) is
> placed in "vs2008\include", but projects expects it in
> "..\..\..\include\tesseract_versionnumbers.vsprops"...
Right, its a bit confusing because the instructions in
vs2008\doc\setup.html assume the presence and use of a package that
doesn't exist yet. Its going to be *your* job to create
tesseract-ocr-3.02-vs2008.zip. This will be structured as follows:
include\
tesseract\
stdint.h
leptonica_versionnumbers.vsprops
tesseract_versionnumbers.vsprops
tesseract-3.02\
vs2008\
(all the stuff from my vs2008 archive)
And it's meant to be extracted on top of the extracted contents of
leptonica-1.68-win32-lib-include-dirs.zip. See vs2008\doc\setup.html
since that has a complete list of what the directories will contain.
My VS2008 Solution uses relative path to find everything it needs and
some of those paths result in it looking *OUTSIDE* of the
tesseract-3.02 tree. So its very important that people understand the
basic directory setup they need to use. And I do try to explain all
that in my vs2008\doc\setup.html file.
At this stage, *you* (as someone on the bleeding edge) have to follow
the instructions in
vs2008\doc\setup.html#using-the-latest-tesseractocr-sources. In
particular, the Step which copies the headers is *not* optional for
you. So use the tesshelper.py Python Script (with Python 2.7.x), to
automatically copy the required headers to include\tesseract.
Eventually, you'll also be the one to create the
tesseract-ocr-3.02-win32-lib-include-dirs.zip (for people who don't
want to bother getting and compiling libtesseract, but *do* want to
link with it). That will be composed of:
include\
tesseract\
stdint.h
leptonica_versionnumbers.vsprops
tesseract_versionnumbers.vsprops
lib\
libtesseract302.dll
libtesseract302.lib
libtesseract302d.dll
libtesseract302d.lib
libtesseract302-static-debug.lib
libtesseract302-static.lib
In other words, it will be exactly analogous to my Leptonica 1.68
pre-built binary package, leptonica-1.68-win32-lib-include-dirs.zip.
But for now, to build directly from a tesseract-OCR Working Copy
directory (not necessary recommended), you need to have the following
directory structure around it:
include\
all the stuff from the include dir of
leptonica-1.68-win32-lib-include-dirs.zip
tesseract\
stdint.h
leptonica_versionnumbers.vsprops
tesseract_versionnumbers.vsprops
lib\
all the stuff from the lib dir of leptonica-1.68-win32-lib-include-dirs.zip
tesseract-ocr\
vs2008\
And to avoid confusion you really need to delete the repository's
existing vs2008 directory and replace it with *my* vs2008 directory.
On my system, I actually don't build directly in my SVN Working Copy
directory, but copy everything to a separate tree, structured like
above (just to avoid making inadvertent changes to the Repository,
even though I don't even have commit anyway).
> I changed 'class DLLSYM STRING' to 'class CCUTIL_API STRING' as local
> solution for http://code.google.com/p/tesseract-ocr/issues/detail?id=614:
Good. Although the SVN repository needs this fix as well. (Every time
I get an update from the SVN I seem to forget that I have to re-change
that line).
>
> Configuration DLL_Debug created libtesseract302d.dll, tesseract-dlld.exe,
> but produced error for other project ( just errors see dll_debug.log).
> Configuration DLL_Release created libtesseract302.dll, tesseract-dll.exe,
> but produced error for other project ( just errors see dll_release.log).
AHA! I see you didn't read:
vs2008\doc\building.html#building-the-training-applications :P
This explicitly says:
Note
Currently these applications can ONLY be built with the LIB_Debug
and LIB_Release configurations. If you try to use a DLL configuration
you’ll get “undefined external symbol” errors.
And... This isn't my fault. Since in the unix world creating shared
libraries has nothing to do with changing the visibility of classes,
the unix guys haven't really thought very carefully about what happens
on Windows when DLLs are created. So... they have only exported the
TessBaseAPI & STRING classes. Any application that tries to use any
other class from the DLLs will currently fail (like all the training
apps).
I'm working on a longish post that discusses this important issue, but
it isn't ready yet. To give you a hint read "Why is the new C++
visibility support so useful?" (http://gcc.gnu.org/wiki/Visibility) :)
> Configuration LIB_Debug finished without problem (Build: 11 succeeded, 0
> failed, 0 up-to-date, 0 skipped)
> Configuration LIB_ Release finished without problem (Build: 11 succeeded, 0
> failed, 0 up-to-date, 0 skipped)
>
> APItest solution do not have correct path for leptonica (should be
> '..\..\..\..\include\leptonica' is '..\..\include\leptonica' ) and tesseract
> (points to '..\..\include\tesseract', but there in no
> include\tesseract directory).
Yes, again, APITest has to assume that it has been *copied* to a new
location before use (since it is an example of the typical app which
will live *outside* the tesseract-3.02 tree). So you need to use it in
the following directory structure (as explained in
vs2008\doc\programming.html#apitest-sample):
C:\BuildFolder\
include\
leptonica\
tesseract\
leptonica_versionnumbers.vsprops
tesseract_versionnumbers.vsprops
stdint.h
lib\
(lots of library files)
tesseract-3.02\
APITest\
baseapitester\
baseapitester.cpp
baseapitester.rc
baseapitester.vcproj
resource.h
stdafx.cpp
stdafx.h
targetver.h
APITest.sln
In fact, it would be a good idea to include the APITest (and the
forthcoming APIExamples) folders in their appropriate place in your
tesseract-ocr-3.02-vs2008.zip. :)
I know this is confusing... so, I'll provide you with examples of what
I think the eventual .zip distributions should contain and their
directory layouts.
> idea behind 'port' and 'include' directories is that 'include' has files
> needed only for VC++ 2008 (they are problem for mingw) and 'port' has files
> needed for building on windows... This should be changed/improved because
> leptonica headers are include directory and there are needed also for mingw
> ;-) So you can changed it as suitable.
Right, I think I unilaterally already did this :P
+ The leptonica headers are no longer any part of tesseract-ocr but
need to be downloaded separately.
+ The vs2008\include directory is *only* used for things that need to
be copied to the "public" include directory. It is *not* used by the
compiler (which instead references the "public" include folder).
+ And the vs2008\port directory is needed for things just to build
Windows (like mathfix.h & version.h). It *is* used by the VC++
compiler. Dunno about the MinGW compiler.
Since my initial post, I've added quite a bit of new documentation
(mostly to the programming libtesseract & tools sections), added the
beginnings of a new APIExamples solution (showing how to use Leptonica
& TessBaseAPI), and fixed a minor issue in the VS2008 Solution. I hope
to release my next version tomorrow some time.
-- Tom
Tom Powers
documentation for tesseract-3.02 alpha is now at:
http://www.mediafire.com/?23xko65yhmxocgm
This release is really only for the more adventurous (or desperate).
In particular, you'll need to read the vs2008/doc/setup.html page,
especially "Using the latest Tesseract-OCR sources" which explains the
steps required to download and use the SVN sources. Most of you should
just probably wait a few weeks for the "real" release.
On the other hand, I'd appreciate it if those of you who aren't
planning on being on the bleeding edge, would still download the
package and take a look at the documentation in the vs2008\doc folder.
Comments from "newbies" to building tesseract on Windows using Visual
Studio 2008 (or VC++ 2008 Express Edition) would be helpful.
For those who haven't been following the thread on the tesseract-dev
list, this enhanced VS2008 Solution among other things:
+ Is a completely new Visual Studio 2008 solution created from scratch.
+ Has (mostly) full HTML documentation in the vs2008\doc directory,
built using the Sphinx Python Documentation Generator. Only the
documentation for the work-in-progress APIExamples Solution needs to
be finished at this point (I think).
+ Has LIB_Release, LIB_Debug, DLL_Release, and DLL_Debug build
configurations.
+ Creates a single libtesseract library (removes generation of the
twelve sub-libraries).
+ Adds Version Resources to all DLLs and applications.
+ Removed inclusion of the Leptonica libraries. They now have to be
downloaded separately.
Besides adding some more documentation, the changes from my initial release are:
+ All "internal" projects (everything *except* APITest) now refer to
vs2008\include\tesseract_versionnumbers.vsprops and
vs2008\include\leptonica_versionnumbers.vsprops instead of the "public"
include directory as per Zdenko's request.
+ stdint.h was removed from vs2008\include since it is no longer needed
to build Leptonica.
+ inttypes.h was removed from vs2008\include since it isn't needed
to build Leptonica.
+ All references to __MSW32__ were removed.
+ Move mathfix.h from vs2008\include to vs2008\port
+ The list of "public" header files that are required to build
"external" applications is now limited to the following 13 files::
api\apitypes.h
api\baseapi.h
ccmain\thresholder.h
ccstruct\publictypes.h
ccutil\errcode.h
ccutil\fileerr.h
ccutil\host.h
ccutil\memry.h
ccutil\platform.h
ccutil\serialis.h
ccutil\strngs.h
ccutil\tesscallback.h
ccutil\unichar.h
This version assumes that issue 635 at
http://code.google.com/p/tesseract-ocr/issues/detail?id=635 has been
fixed. However, it probably *only* affects APITest and so can for the
most part be ignored.
--Tom
zdenko podobny
Tom Powers
> So to make it easier:
> it is in svn (excluding APItest - it will be included in something like
> tesseract-3.02-win32-lib-include-dirs.zip - maybe during week I will create
> and upload some alpha version for testing).
> Wiki, README etc was not update to 3.02 version.
> vs2008\doc is not served as html - I will try to fix it ;-)
>
> And big thanks to Tom for his contribution and investigations!
>
> Zdenko
Looks good! You've indeed made the "Visual Studio 2008 Developer Notes
for Tesseract-OCR" available directly [1]. There is no need to
download the SVN to view them, and other people can create links to
these pages (like from the Wiki) :)
At this point I don't anticipate any more changes to the VS2008
directory other than to VS2008\doc, VS2008\APITest, and
VS2008\APIExamples. I was progressing pretty well, but my C++-fu has
never been very great --- I'm more comfortable in Python, C, C# --- so
I started to investigate the "right" way to use C++. And then... I
discovered that the C++11 standard has just been ratified [2] and
compilers (including Visual C++ [3][4]) are already starting to
include some of its features.
Therefore, in order to get this done soon (this week say) it looks
like I should just forge ahead, however clumsily (and not bother
reading More Effective C++ by Meyers). While my examples should show
how to use most of TessBaseAPI, they won't necessarily be great
examples of C++ use --- more like using C with a C++ compiler :)
[Aside: Does anyone know of an easy way to add Doxygen "documentation
comments" to functions/methods using Visual Studio 2008?
AtomineerUtils [5] looks nice but while cheap it's not free.]
[1] http://tesseract-ocr.googlecode.com/svn/trunk/vs2008/doc/index.html
[2] http://www2.research.att.com/~bs/C++0xFAQ.html
[3] http://msdn.microsoft.com/en-us/library/dd465215.aspx
[4] http://msdn.microsoft.com/en-us/library/hh409293(v=vs.110).aspx
[5] http://www.atomineerutils.com/products.php
-- Tom
Wout Bittremieux
If you recall correctly, last week I had some problems using Tesseract and Leptonica in Visual Studio 2010. I built Tesseract in particular using Visual C++ 2008 Express Edition. The build procedure was successful and I was able to use the libraries generated by all four build configurations in your APITest project. However, strangely enough, I was only able to use the dynamic libraries (debug and release) in my Visual Studio 2010 project (of course when keeping in mind the correct procedure for freeing up the memory allocated by these libraries). However, strangely enough, using the static libraries resulted in several 'unresolved external symbol' errors.
Furthermore, I tried to build Tesseract using Visual Studio 2010 as well. Converting the solution from Visual Studio 2008 to Visual Studio 2010 is relatively straight-forward, no significant errors were experienced. The only thing I had to adjust was the post-build event that copied the library to BuildFolder\lib because the semantics the $(TargetPath) have been changed in Visual Studio 2010. After I adjusted these events, building Tesseract in Visual Studio 2010 was simply a matter of following your guidelines.
Using the libaries built in Visual Studio 2010, I was able to successfully include the two release libraries (static and dynamic) in my own project. The two debug versions do not work on a machine without Visual Studio 2008 because of the absence of MSVCR90D.DLL, as was expected.
Op donderdag 23 februari 2012 18:02:32 UTC+1 schreef Tom Powers het volgende:
TP
> I was able to successfully build Tesseract revision 684 using the procedure
> you outlined in your documentation.
>
> If you recall correctly, last week I had some problems using Tesseract and
> Leptonica in Visual Studio 2010. I built Tesseract in particular using
> Visual C++ 2008 Express Edition. The build procedure was successful and I
> was able to use the libraries generated by all four build configurations in
> your APITest project. However, strangely enough, I was only able to use the
> dynamic libraries (debug and release) in my Visual Studio 2010 project (of
> course when keeping in mind the correct procedure for freeing up the memory
> allocated by these libraries). However, strangely enough, using the static
> libraries resulted in several 'unresolved external symbol' errors.
Glad to hear you were able to correctly build using VC++2008 Express,
That is a bit strange, but you'd have tell me what "unresolved
external symbol" errors you are seeing for me to comment further.
>
> Furthermore, I tried to build Tesseract using Visual Studio 2010 as well.
> Converting the solution from Visual Studio 2008 to Visual Studio 2010 is
> relatively straight-forward, no significant errors were experienced.
Great.
> The
> only thing I had to adjust was the post-build event that copied the library
> to BuildFolder\lib because the semantics the $(TargetPath) have been changed
> in Visual Studio 2010. After I adjusted these events, building Tesseract in
> Visual Studio 2010 was simply a matter of following your guidelines.
Hmmmm. I'll have to see if the VS2008 project can be adjusted to avoid
this. This error doesn't appear when converting leptonica, so maybe I
botched something.
> Using the libaries built in Visual Studio 2010, I was able to successfully
> include the two release libraries (static and dynamic) in my own project.
> The two debug versions do not work on a machine without Visual Studio 2008
> because of the absence of MSVCR90D.DLL, as was expected.
Are you saying that even after installing VC++2008 Express Edition,
you still didn't have access to the MSVCR90D.DLL? I would have thought
(as I mentioned in my reply to your other post), that installing
VC++2008EE would fix your problem. On the other hand, from what I saw
while researching your earlier question, I gather that all sorts of
slightly weird edge cases can disable debugging:
+ installing VC++2008EE in the wrong order, along with VS
+ or not also installing the Service Packs in the right order
+ or strangely having your project reside on a network drive rather
than a local drive
+ turning on incremental linking (it works if people turn off
incremental linking?)
+ generating a manifest
See http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/8f08777b-1c4d-4e10-89a2-f7bc95cf5e98/
for a really strange thread wherein people mention the problems
they've seen and the weird solutions they've come up with.
Wout Bittremieux
Are you saying that even after installing VC++2008 Express Edition,
you still didn't have access to the MSVCR90D.DLL? I would have thought
(as I mentioned in my reply to your other post), that installing
VC++2008EE would fix your problem. On the other hand, from what I saw
while researching your earlier question, I gather that all sorts of
slightly weird edge cases can disable debugging:+ installing VC++2008EE in the wrong order, along with VS
+ or not also installing the Service Packs in the right order
+ or strangely having your project reside on a network drive rather
than a local drive+ turning on incremental linking (it works if people turn off
incremental linking?)+ generating a manifest
See http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/8f08777b-1c4d-4e10-89a2-f7bc95cf5e98/
for a really strange thread wherein people mention the problems
they've seen and the weird solutions they've come up with.
On a machine without VC++2008EE and only VS2010, debugging doesn't work, because of the absence of MSVCR90D.DLL of course.
Op woensdag 29 februari 2012 20:56:58 UTC+1 schreef TP het volgende:
On Wed, Feb 29, 2012 at 3:17 AM, Wout Bittremieux wrote:
> I was able to successfully build Tesseract revision 684 using the procedure
> you outlined in your documentation.
>
> If you recall correctly, last week I had some problems using Tesseract and
> Leptonica in Visual Studio 2010. I built Tesseract in particular using
> Visual C++ 2008 Express Edition. The build procedure was successful and I
> was able to use the libraries generated by all four build configurations in
> your APITest project. However, strangely enough, I was only able to use the
> dynamic libraries (debug and release) in my Visual Studio 2010 project (of
> course when keeping in mind the correct procedure for freeing up the memory
> allocated by these libraries). However, strangely enough, using the static
> libraries resulted in several 'unresolved external symbol' errors.Glad to hear you were able to correctly build using VC++2008 Express,
That is a bit strange, but you'd have tell me what "unresolved
external symbol" errors you are seeing for me to comment further.
Furthermore, using the static libraries built with VC++2008EE in a VC++2008EE project (f.e. APITest), again no linking errors occur and they work correctly.
TP
Okay. Good. That's what I thought (and I'll fix the VS2010 Notes to
reflect the need for MSVCR90D.DLL when debugging and how installing
VC++2008EE can solve the problem).
Looks to me like some file in your project isn't properly including
the correct standard C++ headers. You need to add at least
#include <string> and maybe #include <iostream>.
blavatsky3
Do you know if dawg2wordlist is going to be ported or migrated into vs2010 project ?
Do have copy of dawg2wordlist.exe I can try out please ?
kind regards
Richard
blavatsky3
I was wondering if you send me the vs2010 source files for Tesseract-OCR project ?
Have you been able to compile dawg2wordlist.exe using vs2010 ?
Could I have a copy of that too please ?
kind regards
Richard
blavatsky3
Thanks
Richard