(cross-posting to dev-gaia as there's developers doing full builds there
too)

TL;DR Building B2G doesn't require a ton of memory anymore and won't
slow your machine to a crawl. You can now build B2G with as little as
2GB of memory provided you run ./build.sh -j2 and anybody with older 4GB
laptops should now be fine with the default number of jobs. To make sure
this works correctly run ./repo sync and clobber your objdir-gecko
directory before the next build.

Long story: bug 888698 was fixed and with it the annoying problem of
Gecko being built using a hard-coded number of 16 jobs which among other
problems required a lot of memory since unified builds have landed. This
often led to OOM errors while building on boxes with less than 8GB of
memory and was a recurring issue with contributors trying to build B2G
the first time or within a VM because there was no simple way around it.

Now the number of jobs used to build gecko is the same as the number
given to build.sh (by default that's the number of logical cores + 2).
For most people this means that building B2G will require less resources
but those among you with epic dual-Xeon workstations with more than 16
logical cores should actually expect a speed-up (and an increase in
memory consumption).

Note that this also means that ./build.sh -j1 finally works as expected
properly stopping when it encounters the first error.

BTW all of the above applies to invoking make directly in the top-level
B2G directory and is not restricted to build.sh.

 Gabriele

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to