Android NDK performance

Started by
1 comment, last by Serapth 11 years ago

I've recently been working quite a bit in Haxe and I've noticed something really weird. The development machine I am using is a 2012 Macbook Air, dual booting Windows 7 and MacOS 10.8.2. I've been working about equally in both platforms and noticed something rather stunning...

The Android NDK ( C++ dev kit ) is about 3x slower to compile on MacOS than it is on Windows. This seems really shocking to me as I believe the NDK requires a bolt on OS extension ( Cygwin ), while MacOS obviously has a native terminal. I would obviously think gcc on MacOS would be better optimizied than the Windows version...

At this point I am simply curious what is going on... anyone else working with the Android NDK... have you noticed the same speed differences, and is there any way to make Gcc on MacOS well... faster?

Advertisement

Disable the optimizer and try again.

There are known issues with the optimizer performance. Sadly the optimizer will often churn on a file and then actually produce worse-performing binaries than the non-optimized build.

Do you mean in terms of -O command line switches?

If so, that may not be an option in this case as its actually NME that is invoking the compiler in this case.

This topic is closed to new replies.

Advertisement