I'm just not sure what the right strategy is to combine these with the
NDK. We already have crystax's full C++ support, and mingw-android's
port to MinGW. Do we need yet another on that brings in CodeSourcery's
patches? I guess we'll have to. But I wish these things would become
standard in the NDK itself so we can have the best toolchain available
to build our apps.
> You received this message because you are subscribed to the Google Groups "android-ndk" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-ndk...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-ndk?hl=en.
I've just been looking at the latest source for their toolchain and
the build scripts. They ship a tarball of their modified gcc. Has
anyone tried to apply the Android patches to it?
Also, they do a Canadian cross from Linux to produce the MinGW
binaries for Windows. Combine that with crystax's work and the CS
performance improvements, we could end up with one hell of a
On Sat, Oct 2, 2010 at 7:53 PM, teknoraver <techn...@gmail.com> wrote:
After reading this thread, I experimented with ARM-2010q1 build of CodeSourcery (lite version). The integration was easy. Here is what I did to get it working:
Got the TAR package from:
- Extracted the TAR package into $NDK/build/prebuilt/linux-x86
- cd $NDK/build/toolchains
- cp -Rp arm-eabi-4.40 arm-2010q1
- cd arm-2010q1
- Edit setup.mk, and changed TOOLCHAIN_PREFIX to ... arm-none-linux-gnueabi-
To do a quick test
- export NDK_TOOLCHAIN=arm-2010q1
I didn't do extensive testing, but I didn't see much performance improvement in my application, but this is highly application related.
Does this setup looks similar or is there anything I missed to tune?