Creating an Android port will be useful, as it will allow me to use the Cainteoir Engine library to create several different applications.
A successful port will include support for running the tests on Android as well to ensure compatibility. Ideally, the tests/harness.py file should be modified to allow running the tests on android using e.g. adb.
Certain things like metadata handling will need to be done differently (maybe by distributing a cut-down version of the shared-mimetype-database to detect only the files that Cainteoir Engine supports). Others (like poppler and ogg/vorbis support) will either need the corresponding libraries ported to Android or excluded from the Android build. Not sure what to do about gettext support.
This port should be done incrementally, one source file at a time. For example, starting with utf8.cpp.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1026784-port-to-android?utm_campaign=plugin&utm_content=tracker%2F254961&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F254961&utm_medium=issues&utm_source=github).
Creating an Android port will be useful, as it will allow me to use the Cainteoir Engine library to create several different applications.
A successful port will include support for running the tests on Android as well to ensure compatibility. Ideally, the
tests/harness.pyfile should be modified to allow running the tests on android using e.g.adb.Certain things like metadata handling will need to be done differently (maybe by distributing a cut-down version of the shared-mimetype-database to detect only the files that Cainteoir Engine supports). Others (like poppler and ogg/vorbis support) will either need the corresponding libraries ported to Android or excluded from the Android build. Not sure what to do about gettext support.
This port should be done incrementally, one source file at a time. For example, starting with utf8.cpp.