From 7e73d5799b1e3245052e418585aaa0bd2b6ac8aa Mon Sep 17 00:00:00 2001
From: Daniel Micay <danielmicay@gmail.com>
Date: Thu, 23 Apr 2020 16:48:48 -0400
Subject: [PATCH] make no longer controls jobs

---
 static/build.html | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/static/build.html b/static/build.html
index 30520e45..fdb34d54 100644
--- a/static/build.html
+++ b/static/build.html
@@ -400,11 +400,7 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/
 
             <pre>rm -r out</pre>
 
-            <p>Start the build process, with -j# used to set the number of parallel jobs to the
-            number of CPU threads. You also need 2-4GiB of memory per job, so reduce it based on
-            available memory if necessary:</p>
-
-            <pre>make target-files-package -j20</pre>
+            <pre>make target-files-package</pre>
 
             <p><strong>For an emulator build, always use the development build approach below.</strong></p>
 
@@ -419,7 +415,7 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/
             bootloader unlocked and flashing the raw images that are signed with the default
             public test keys:</p>
 
-            <pre>make -j20</pre>
+            <pre>make</pre>
 
             <p>Technically, you could generate test key signed update packages. However, there's
             no point of sideloading update packages when the bootloader is unlocked and there's no
@@ -527,7 +523,7 @@ cd ../..</pre>
 
             <p>Build the tool needed to generate A/B updates:</p>
 
-            <pre>make -j20 brillo_update_payload</pre>
+            <pre>make brillo_update_payload</pre>
 
             <p>Generate a signed release build with the release.sh script:</p>