I am reviewing Tesseract for inclusion in a suite of tools for solving factory automation applications. I notice that the code is is a high state of flux as it moves to V3.x. and I sympathize with the team as this painful transition is accomplished.
As a part of my review, I gathered the SVN repository and built the three configurations (vs2008) and was surprised by two facts: First, the builds generate about 700 warnings each. As a professional engineer, I maintain that released code should be edited to eliminate ALL warnings (leaving at most a few). I have been generating high quality code for 40 years (true!!) with that rule and have never regretted the result. Question: Will this code be edited to reduce the noise level of these warnings? Second, and more troubling, is the fact that after building all configurations, I find NO DLL files with which to bind. I can link to a collection of LIB files in the static build but there is nothing but an executable in the release-dynamic configuration. Question: Is version 3.x going to support a DLL binding? If so, when will the configuration files be edited to accomplish that? -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en.
