Experimental Toolchains and Guide for Android Kernel Building
We here on XDA love innovation and development. We especially love it when one of our members decides to push development on the Android mobile platform further. XDA Recognized Developer ezterry has done just.
The developer has not only created detailed, cross-platform guides on setting up a development environment in Linux, Windows, and MacOSX; but he also provided the latest experimental toolchains for compiling, not normally found when downloading pre-compiled packages directly from Google.
When I asked him about the benefits of this newer toolchain his response was this:
The newer compiler ought to generate more efficient code from the same original C source. This means hopefully a kernel built with these versions of the toolchain will run faster, allowing kernel tasks to complete sooner, and with luck allow more CPU to go to your applications and games when your system is under load, and spend more time sleeping when your system isn’t under load.
He also went on to explain why someone creating a new environment should use his packages rather than the normal pre-built ones:
The cygwin toolchains are more infrequently built, and both that and the Linux one matches, thus other users can participate on the same kernel from the two different computer OS’s.
These are compiled in the same manner as the toolchains Google includes pre-built. Thus we are more assured the compiler knows about Android conventions when they differ from other ARM Linux builds. Ezterry also explained that not only did he go through all of this work to develop a better kernel for the Acer Iconia A500 Tab, but:
…to provide building instructions to both developers that are running on Linux boxes (as nearly all developers building from source are today) as well as allowing Windows developers with Cygwin installed to be able to build the kernel, and hopefully start introducing themselves to the kernel and using git on the systems they are more used to.
The guides are quite detailed, but if you feel ready for it, head on over to the original thread and get your development on.