6

Android-NDK ships its own compiler to build the native code. The version shipped with my current android-NDK installation is arm-linux-androideabi-g++ (GCC) 4.6.x-google 20120106 (prerelease), I guess it's a fork of GCC 4.6.

What are the differences between it and a regular (vanilla) GCC 4.6? Is it producing better code for ARM platforms?

I'd like to use other compilers to build software for android, like vanilla GCC 4.7 or Clang, since they have a better support of C++11 and implement some features I'm struggling to use (like template aliases).

  1. Is it possible to use the latest vanilla GCC or Clang, to build the native code for Android? What parameters should I use?

  2. What are the cons of using a compiler different from the one shipped with android-SDK?

peoro
  • 25,562
  • 20
  • 98
  • 150

2 Answers2

2

Android GCC is customized for the android as all the features in the GCC are not supported by the native Android. I dont think there is a possibility, you can post the same in the android ndk google groups where your answers will be replied by the Google Android Developers.

They were suggesting that we can make use of the cross compilers for compiling the android code with out using the android ndk.

Suman
  • 4,221
  • 7
  • 44
  • 64
  • A proposal, but not high-priority: Port LLVM's libc++ to the Android NDK (and platform) [http://code.google.com/p/android/issues/detail?id=36496](http://code.google.com/p/android/issues/detail?id=36496) – douyw Oct 23 '12 at 16:08
2

Just a heads-up: google added clang3.1 in Revision 8c of the Android NDK. It's in "experimental" stage now, but easy to try out (and probably will be better supported in the near future, hopefully with a proper port of libc++, too).

mitchnull
  • 6,161
  • 2
  • 31
  • 23