Hello Jon,
On Thu, 26 Apr 2012 15:13:34 +0100 "Jon Medhurst (Tixy)" tixy@linaro.org wrote:
On Thu, 2012-04-26 at 12:25 +0300, Paul Sokolovsky wrote:
Hello,
On Thu, 26 Apr 2012 00:32:14 +0530 Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 25 April 2012 13:59, Paul Sokolovsky paul.sokolovsky@linaro.org
Google says 16Gb is the requirement, linaro-android-build-cmds.sh really should check and refuse to run otherwise.
I build android on my 4gb ram laptop in 2 hrs.
Build, like your working directory, or rebuild from scratch (a new checkout)? Can't believe that, the checkout alone may take more ;-). But if you know some trick, let us know - maybe we can go from very expensive XLARGE instances to LARGE.
As an experiment I booted my 8GB laptop with mem=4096M and built Android from clean in 55 minutes. That was with make -j4 and memory usage came perilously close to the 3.5GB that the 'free' command said was the total system RAM. (Note, I don't have swap enabled so all this worked in real memory.)
With make -j8 the build failed, though I was also using Mumble at the time as well.
Ok, I also set up a build on LARGE (instead of our usual XLARGE) instance: https://android-build.linaro.org/jenkins/job/pfalcon_vexpress-rtsm-ics-gcc46...
So, it works, but takes twice as much time (4:15h). EC2-wise, that will be rounded to 5hrs, so no economical effect. So, doesn't make any sense to switch to LARGE build slaves.
But coming back to the point of generating dosk images in the cloud, we could set up in the similar manner SMALL instance, allow sudo on it, and generate images there with separate job (which would probably generate images for all recent builds in a batch).