I believe that there is no true need to change anything. To run unittest (and even training) on Android, it's enough to choose __ANDROID_API__=28 (or higher). Methinks that this is a reasonable restriction. The production version of the library can still be built with __ANDROID_API__=16 and exclude fileio.cpp
Alex On Wednesday, August 7, 2019 at 12:50:50 PM UTC+3, René Hansen wrote: > > Agreed. Maybe the real solution after all, is to drop the usage of glob, > and go for a portable solution? > > This is how I got around it initially. Not the best code though: > > https://github.com/tesseract-ocr/tesseract/compare/4.1.0...rhardih:4.1.0-rhardih > > On Wed, 7 Aug 2019 at 10:56, 'Stefan Weil' via tesseract-ocr < > tesser...@googlegroups.com <javascript:>> wrote: > >> It's a pity that I did not see this discussion earlier. I understand that >> old Android now builds fine. On the other side, the Appveyor CI build for >> Windows was now broken, and unittest still no longer build. That's not a >> good result. :-( >> >> I therefore suggest to go back to my commit >> <https://github.com/tesseract-ocr/tesseract/commit/7a2f8d90102b7ce436f1dca96ef4c5cd312307e1> >> >> which moved fileio.* from training to ccutil. Then conditional compilation >> for Android can be added to fileio.cpp. How should it look like? >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/7bf1d57e-80bb-4eb3-b696-73e7b5aaf2be%40googlegroups.com.
