I was able to compile and use 4.0.0-rc3 on Android (tested on a virtual
device with API level 26 and on a real API level 29 device).
Basically, I used NDK CMake toolchain to build it, but I had to make minor
changes.
${SDK}/cmake/3.6.4111459/bin/cmake -G"Android Gradle - Ninja" -
DCMAKE_MAKE_PROGRAM=${SDK}/cmake/3.6.4111459/bin/ninja -
DCMAKE_TOOLCHAIN_FILE=${NDK}/build/cmake/android.toolchain.cmake -
DANDROID_ABI=${ARCH} -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/opt/output/${ARCH}/ -
DCMAKE_INSTALL_PREFIX=/opt/${ARCH} -DBUILD_TRAINING_TOOLS=OFF -DBUILD_TESTS=OFF
-DANDROID_PLATFORM=android-26 -DANDROID_STL=c++_static ..
Out of the box, this build would fail because of a dependency on *glob**()*
std call (in File::DeleteMatchingFiles).
While it might work by simply changing -DANDROID_PLATFORM=android-28, I noticed
that this function is only used for training so I removed it and it worked
OK.
On Tuesday, October 16, 2018 at 3:48:05 AM UTC-4, zdenop wrote:
>
> Is here anybody who build&use tesseract on Android?
> I would like to solve:
> https://github.com/tesseract-ocr/tesseract/issues/1393
>
> Zdenko
>
>
> ne 14. 10. 2018 o 19:48 Zdenko Podobny <zde...@gmail.com <javascript:>>
> napísal(a):
>
>> RC 3 is ready[1].
>>
>> Please test, test, test.
>> Especially if you are building tesseract on other platform than linux or
>> windows (cppan+cmake).
>>
>> If you have any patch for the current code please provide it ASAP (via
>> pull request or attach patch to issue tracker) for evaluation.
>> Report problems ASAP in issue tracker, so we can fix it until finale
>> release.
>>
>> [1] *https://github.com/tesseract-ocr/tesseract/releases/tag/4.0.0-rc3
>> <https://github.com/tesseract-ocr/tesseract/releases/tag/4.0.0-rc3>*
>>
>>
>> Zdenko
>>
>>
>> ne 7. 10. 2018 o 21:18 Zdenko Podobny <zde...@gmail.com <javascript:>>
>> napísal(a):
>>
>>> RC 2 is ready[1].
>>> Please test, test, test. Especially if you are wrapping tesseract and
>>> creating/providing packages.
>>> If you have any patch for the current code please provide it ASAP (via
>>> pull request or attach patch to issue tracker) for evaluation.
>>> Report problems ASAP in issue tracker, so we can fix it until finale
>>> release.
>>>
>>> [1] https://github.com/tesseract-ocr/tesseract/tree/4.0.0-rc2
>>> <https://github.com/tesseract-ocr/tesseract/tree/4.0.0-rc1>
>>>
>>> Zdenko
>>>
>>>
>>> ne 30. 9. 2018 o 19:50 Zdenko Podobny <zde...@gmail.com <javascript:>>
>>> napísal(a):
>>>
>>>> RC 1[1] ready.
>>>> Please test, test, test. Especially if you are wrapping tesseract and
>>>> creating/providing packages.
>>>> Report problems ASAP in issue tracker, so we can fix it until finale
>>>> release.
>>>>
>>>> [1] https://github.com/tesseract-ocr/tesseract/tree/4.0.0-rc1
>>>>
>>>>
>>>> Zdenko
>>>>
>>>>
>>>> so 22. 9. 2018 o 17:06 Zdenko Podobny <zde...@gmail.com <javascript:>>
>>>> napísal(a):
>>>>
>>>>> Hello,
>>>>>
>>>>> I would like to thank all who share their thought about releasing new
>>>>> version of tesseract [1]. I took my time and I decided we should make
>>>>> release at the middle October 2018 (14-21...).
>>>>>
>>>>> This should means that no new features will be applied to current
>>>>> code. There is not time for testings. Anyway please feel free to send
>>>>> your
>>>>> patch/PR - it will included after 4.0 release.
>>>>>
>>>>> There are several ways, how people can contribute to this process:
>>>>>
>>>>> - *Developers*: go through open issues, try to fix it. Please make
>>>>> a comment when you start do deal with issue, so we can use our
>>>>> capacity
>>>>> efficiently.
>>>>> - *Packagers*: please test if building and packaging process is
>>>>> working fine. If something is broken, try to fix&submit it fast.
>>>>> Please
>>>>> give a note to forum or me directly, where users can find your
>>>>> "product",
>>>>> so we can put information about supported systems to release notes.
>>>>> - *"Wrappers"*: if you are producing wrapper for tesseract, please
>>>>> give a note to forum or me directly if you support tesseract 4: I
>>>>> would
>>>>> like to promote your work.
>>>>> - *"No code" developers*:
>>>>> - check open issues, test it with the latest code if it still
>>>>> valid report, prepare test case if missing, report duplicates,
>>>>> suggest
>>>>> label etc.
>>>>> - Improve documentation, release notes, man pages etc...
>>>>> - English native speaker: check documentation, release notes
>>>>> etc.
>>>>>
>>>>> Thanks to all who help us to get to this point. I really appreciate
>>>>> all ways of support.
>>>>>
>>>>> [1] https://github.com/tesseract-ocr/tesseract/issues/1423
>>>>>
>>>>> Zdenko
>>>>>
>>>>
--
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.
To post to this group, send email to tesseract-ocr@googlegroups.com.
Visit this group at https://groups.google.com/group/tesseract-ocr.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tesseract-ocr/4954afff-e46e-4c76-bf9d-535e9fe53cb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
