Android 4.0 Ice Cream Sandwich A.K.A ICS, the newest build and the one we have on our lips right now. The source code should be released fairly soon and developers out there will be itching to get hold of it and get modifying, building, tinkering and compiling us Android users some fantastic roms for devices that will see ICS officially and also the ones that won’t.
CyanogenMod have already said they will be working on CM9 for a whole host of possible devices, HTC developers, Motorola developers and many more will want to get there developing machines read… well, if you haven’t heard or may have missed it, your going to need a bit of Wonga to upgrade to a lot more if your not near what Ice Cream Sandwich will need.
Building Android source takes a lot of resources and according to Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, at Google, here is what you will need and it’s a pretty hefty amount of hardware.
Some advance information so that people can prepare machines ahead of
time for the future ICS release that we’ve recently announced:
ICS will be a much larger release than any previous Android release.
That means that it will also put a much bigger strain on the machines
that people use to compile it. As a rule of thumb, everything about
ICS in AOSP will be about twice as large as it was for Gingerbread.
Here are some preliminary numbers. Final numbers will probably be a
bit different, but those should be a reasonable first-order
approximation. Of course, your mileage may vary.
-6GB of download.
-25GB disk space to do a single build.
-80GB disk space to build all AOSP configs at the same time.
-16GB RAM recommended, more preferred, anything less will measurably
benefit from using an SSD.
-5+ hours of CPU time for a single build, 25+ minutes of wall time, as
measured on my workstation (dual-E5620 i.e. 2x quad-core 2.4GHz HT,
with 24GB of RAM, no SSD),
Naturally, if you plan to work on multiple branches (e.g. ICS release,
ICS development branch and AOSP master branch), you need to plan for
disk space accordingly, and you could easily end up using 250+GB.
If you use ccache, you need to expect it to use 3+GB for a single
build. Just about any non-trivial use case will require 10+GB to get a
good hit rate. If you work on a broad variety of branches or devices
and expect to routinely do full clean builds, tens of GB will be
useful, especially if you make local changes to any of the C/C++ code.
Finally, in terms of operating systems, things haven’t changed since
Gingerbread: 64-bit Ubuntu 10.04 and MacOS 10.6 (with XCode 3) are the
ones most likely to work.
Wow, that’s a big amount and it’s twice as much as Gingerbread required so any budding developers or pro’s that haven’t heard what they may need, if you haven’t got a bigger enough spec machine set up and want to be developing in time for Ice Cream Sandwich you may want to ask for an early Christmas present in some upgrades.