This is mostly done. However not able to figure out __atomic_*_8 linking issues for mips and armeabi architectures. Both of these are old and very rarely used architectures.

Marking this for review.
Following works:

• armeabi-v7a
• arm64-v8a
• x86
• x86_64
• mips64

Still not able to figure out how to get armeabi and mips architecture working. Based on https://code.google.com/p/android/issues/detail?id=182094, providing -latomic should have done the trick, but does not seem to resolve the issue. I might not be looking at some wrong place in android toolchain.

I am actually fine with not having support for these 2 architecture, if we can not find a way to fix the builds for these, since there are not many devices based on these architectures.

@hjanetzek Since you already on this, can you review this and merge?

Thanks

Glad all the architectures are working now! Now that I'm looking at all of them in the CI builds, we may want to pare down the number of architectures that we build - 25 minutes is just too long to wait for a CI build.

I think a reasonable set of architectures to support for now would be:

• ARMv7
• x86
• ARM64

If someone requests a MIPS build, then we can think about those ;)

So.. ready to merge once you decided which platforms to build :)

I think we will wait on this at least until tomorrow to discuss in the mobile meeting for what architectures to build and what should be the appropriate strategy to have multiple architecture deployment, considering it costs us ~4mins per architecture on travis.

So based on the discussion in the mobile meeting today, I have modified the travis deployment script to do builds for armeabi, armeabi-v7a (default build), arm64-v8a and x86.

Deployment will only happen for the master branch builds.

Will merge once travis goes green.