Thanks, Tom. Appreciate the instructions and I'll give them a try. Any idea when the 'significant changes in the works' will be ready for release.
Shree Shree Devi Kumar ____________________________________________________________ भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com On Wed, May 8, 2013 at 2:51 PM, TP <wing...@gmail.com> wrote: > > On Tue, May 7, 2013 at 7:43 PM, Shree Devi Kumar <shreesh...@gmail.com>wrote: > >> Anyway, That was the reason for wanting to follow the program in VS2008. >> If you know of some instructions/tutorial to do that and can point me to >> it, that will be great. > > > Visual Studio is generally agreed to have the state of the art debugger > (even by people who otherwise hate programming on Windows). It's really not > that hard to use. Other than my "Debugging Tips" [1] in the docs you > referred to earlier which is more specific to stepping into Leptonica code > (you probably don't need to do this for your particular problem), I'd say > just: > > 1) Make sure you build the Solution using the LIB_DEBUG configuration. > > 2) Set the application you want to debug by right clicking on its Project > and choosing "Set as Startup Project". > > 3) Right-click that project and choose Properties, to see its Property > Pages. > > a) In the Debugging section, set "Command Arguments" and maybe "Working > Directory" > > 4) In the file your interested in, click on the left margin to set a > breakpoint at that line. > > 5) Hit <F5> to start debugging. Or just right click the Project, choose > Debug -> Step Into new instance. > > Lots more details about debugging with Visual Studio can be found via > Google. > > That said, tesseract is *very* complicated code with little implementation > documentation. I know from personal experience that trying to figure out > how it works by reading the code and stepping through it can be extremely > painful. The training parts of tesseract are even less documented, use > proprietary training files, and there are hints in the dev mailing list > that significant changes are in the works. > > I eventually gave up, partly because I don't particularly have any > interest in custom OCR. My main interest is supporting the Leptonica Image > Processing library on Windows, and I volunteered to create a better Visual > Studio solution for tesseract (since it is one of the most popular client > apps). > > [1] > http://tesseract-ocr.googlecode.com/svn/trunk/vs2008/doc/programming.html#debugging-tips > > -- > -- > You received this message because you are subscribed to the Google > Groups "tesseract-ocr" group. > To post to this group, send email to tesseract-ocr@googlegroups.com > To unsubscribe from this group, send email to > tesseract-ocr+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/tesseract-ocr?hl=en > > --- > 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 tesseract-ocr+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to tesseract-ocr@googlegroups.com To unsubscribe from this group, send email to tesseract-ocr+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en --- 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 tesseract-ocr+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
