Hi @no_other_alias, perhaps I can help answer a few of these questions, although I’m pretty far out of the cinder android loop. In any event, glad that you’re willing / able to tackle some of this stuff! The project could really use more android experts.
1: Where is the most recent version of Cinder for Android? Have all the different versions been consolidated into one place? I’d like to have a look at the build process.
I think the official cinder master branch is mostly latest, although the build system is way out of date. When the original android port was completed, Android Studio barely supported C++ and a custom solution was created as workaround. There’re probably breadcrumbs on this forum of different folks who have gotten things to work despite this, and there is this open pull request that we should have but haven’t yet managed to get merged. Perhaps this is the best place to start, although maybe even things have changed since this time.
2: Do we have a centralized repository of outstanding issues?
This is probably the best, although perhaps a bit dated now: https://github.com/cinder/cinder/issues?q=is%3Aopen+is%3Aissue+label%3Aandroid
- Does the removal of boost as a dependency significantly lower the barriers to getting this working?
I think so, if can we remove boost with the latest clang versions in the android ndk. Does it support C++17 /
4: Is there a roadmap for the Camera API? It seems that a lot of cinder apps could benefit from ARCore support etc. and it would definitely be good to be able to share code between Android and Windows apps.
I think this is open to those who have experience here, what is most reliable, efficient and widely usable.
5: What are the main obstacles that you can see to getting this working?
Probably getting the build system updated. I also think that debugging support was a huge issue when I worked on an android port years ago, which I think is related (my issues were largely because we were using the custom build tools, so we have minimal debugger integration).