System requirements to build AOSP

1,395 views
Skip to first unread message

David.Warburton

unread,
Aug 30, 2010, 9:17:48 AM8/30/10
to android-platform
I'm trying to get an idea if my spare computer could build android
AOSP or would choke, it's a 1.8ghz single core system with 768M RAM.
I'm sure it would be pushing it. If this doesn't cut it, what is
recommended hardware? What is minimum hardware? Thanks!

Anthony

unread,
Aug 30, 2010, 11:22:55 AM8/30/10
to android-...@googlegroups.com
A slower computer will just take longer to build. What cuts it is dependent on your patience.


--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.


Jean-Baptiste Queru

unread,
Aug 30, 2010, 12:27:27 PM8/30/10
to android-...@googlegroups.com
A usable starting point is a quad-core with 4GB of RAM (but you're
still looking at hour-long builds). With less RAM than that, it
becomes hard to use all cores at the same time as the system starts to
swap. With less than 1GB, you're likely to see your machine crawl to a
halt even with a sequential build, as some individual build steps
require significantly more RAM than that.

JBQ

> --
> You received this message because you are subscribed to the Google Groups "android-platform" group.
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.
>
>

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

Matthieu Jeanson

unread,
Aug 30, 2010, 8:32:35 PM8/30/10
to android-...@googlegroups.com
I have seen several times machines dying when building the Android framework. One we found was running out of memory (and did not have any swap setup), the other we just reinstalled Ubuntu after scratching our heads for a couple of days...

Any good solution or good story for parallel builds ? Using distcc ? anything else ?

Thanks,
Matthieu

leo-gmail

unread,
Aug 30, 2010, 9:55:31 PM8/30/10
to android-...@googlegroups.com
The basic requirement is RAM >= 2G  .
在 2010-08-30一的 06:17 -0700,David.Warburton写道:

Anders Widebrant

unread,
Aug 31, 2010, 4:36:12 AM8/31/10
to android-...@googlegroups.com
One major memory hog I've seen is the javadoc processes which seem
to clock in at about 400 MB each. Avoiding SDK builds, then, will
probably help reduce choking.

Anthony

unread,
Aug 31, 2010, 11:09:56 AM8/31/10
to android-...@googlegroups.com
On a related note, I replace "javadoc" with "true" in build/core/droiddoc.mk. Speeds up builds and presumably lowers RAM usage.

leo-gmail

unread,
Aug 31, 2010, 9:48:54 PM8/31/10
to android-...@googlegroups.com
You can change variable BUILD_DROIDDOC to some empty file.
./build/core/config.mk:69:BUILD_DROIDDOC:= $(BUILD_SYSTEM)/droiddoc.mk

Or comment " include $(BUILD_DROIDDOC)" statement in ./frameworks/base/Android.mk
./frameworks/base/Android.mk:477:include $(BUILD_DROIDDOC)
./frameworks/base/Android.mk:513:include $(BUILD_DROIDDOC)
./frameworks/base/Android.mk:549:include $(BUILD_DROIDDOC)
./frameworks/base/Android.mk:574:include $(BUILD_DROIDDOC)


在 2010-08-31二的 10:09 -0500,Anthony写道:
Reply all
Reply to author
Forward
0 new messages