-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define minimal tesseract dependancies #2333
Comments
Looks like a bug in baseapi.cpp. |
Leptonica is normally used as a shared library. So it is possible to provide a minimal Therefore I think it is not a build problem, but a problem of the error handling at runtime (which should also be fixed, of course). |
Leponica can handle pnm format without any dependency. |
what about adding minimum versions of python (3.6) and bash (4.4) for training tools? |
@Shreeshrii: we can put info about minimum dependencies to README,md. |
@amitdo : this was exactly reason why I use pnm format: I guess this minimal tesseract&leptonica version is needed by tesseract wrapper (python, java maybe C#) that will use its standard way for opening files and pass only image data to tesseract. |
@stweil : you are right - I did not calculate with scenario with replacing shared leptonica with version with less features (which I did yesterday on linux "successfully"). |
Why bash |
Here are more details if anybody would like to help it:
Assert is because GetPixInternal did not return pix because pixReadMem did not find format of image_data_. Reason for it that image_data_ should be stored with png format which is not available... |
Crash is fixed. |
I tried to build (cmake&clang) tesseract with minimal dependencies, so I build leptonica without any dependencies (not even zlib). Build finished fine,
tesseract -v
produced:But when I run
tesseract test.pnm -
it produced following error messages and than it crashed:These indicates that there are several must dependencies for running tesseract (tiff, png and therefore zlib...) and they have to be checked (bmfCreate and pixReadMem) during configuring build.
More advance approach would to analyze if relevant code could be skipped - but than we should somehow distribute information about not available API (e.g.
ProcessPagesMultipageTiff
).The text was updated successfully, but these errors were encountered: