Open manimaul opened 5 years ago
If you want to be the champion of that effort, you're welcome.
Ok, that is great. I'll take a look into this. Would you prefer sticking with TravisCI to build and publish the artifacts or would you be ok with adding CircleCI in addition to Travis?
Expected behavior and actual behavior.
Android AAR artifacts should be published to Bintray Jcenter. Publishing Android build artifacts to jcenter will enable android developers to quickly use Gdal in Android applications and libraries by declaring the dependency in their
build.gradle
.Ex:
Notes
Travis CI could leverage a Docker Android NDK image (https://github.com/CircleCI-Public/circleci-dockerfiles/tree/master/android/images) to build the AAR. A good example of building an AAR from Gdal is here https://github.com/paamand/GDAL4Android . Release tagged versions should publish to Jcenter from CI.
Operating system
Android