aboutsummaryrefslogtreecommitdiff
path: root/en/setup/build/building.html
diff options
context:
space:
mode:
Diffstat (limited to 'en/setup/build/building.html')
-rw-r--r--en/setup/build/building.html26
1 files changed, 13 insertions, 13 deletions
diff --git a/en/setup/build/building.html b/en/setup/build/building.html
index ab57d087..43054987 100644
--- a/en/setup/build/building.html
+++ b/en/setup/build/building.html
@@ -45,8 +45,8 @@ AOSP release branches from <a
href="https://developers.google.com/android/drivers" class="external">Google's
drivers</a>. These binaries add access to additional hardware capabilities
with non-open source code. To instead build the AOSP master branch, use the
-<a href="https://developers.google.com/android/blobs-preview" class="external">Binaries
-Preview</a>. When building the master branch for a device, use
+<a href="https://developers.google.com/android/blobs-preview" class="external">
+Binaries Preview</a>. When building the master branch for a device, use
the binaries for the <a href="/setup/start/build-numbers.html">most recent
numbered release</a> or with the most recent date.</p>
@@ -89,7 +89,7 @@ lunch aosp_arm-eng
target from the menu.</p>
<p>All build targets take the form <code>BUILD-BUILDTYPE</code>, where the
<code>BUILD</code> is a codename referring to the particular feature
-combination. The BUILDTYPE is one of the following:</p>
+ combination. The <code>BUILDTYPE</code> is one of the following:</p>
<table>
<thead>
<tr>
@@ -122,7 +122,7 @@ debugging</td>
<a href="running.html">Running Builds</a> for detailed instructions on building
Android.</p>
-<p>Build everything with <code>make</code>. GNU make can handle parallel
+ <p>Build everything with <code>make</code>. GNU <code>make</code> can handle parallel
tasks with a <code>-jN</code> argument, and it's common to use a number of
tasks N that's between 1 and 2 times the number of hardware
threads on the computer being used for the build. For example, on a
@@ -138,7 +138,7 @@ make -j4
<p>You can either run your build on an emulator or flash it on a device. Please
note that you have already selected your build target with <code>lunch</code>,
-and it is unlikely at best to run on a different target than it was built
+and it is unlikely to run on a different target than it was built
for.</p>
<aside class="note"><strong>Note:</strong> Remember to <a
@@ -183,11 +183,13 @@ Please follow the machine setup instructions at
************************************************************
</pre>
-<p>This may be caused by:</p>
+<p>Here are the likely causes and solutions:</p>
<ul>
<li>Failing to install the correct JDK as specified in <a
-href="requirements.html#jdk">JDK Requirements</a>.</li>
+href="requirements.html#jdk">JDK Requirements</a>. Make sure you have followed
+the steps in <a href="building.html#initialize">Set up environment</a> and
+<a href="building.html#choose-a-target">Choose a target</a>.</li>
<li>Another JDK previously installed appearing in your path. Prepend the
correct JDK to the beginning of your PATH or remove the problematic JDK.</li>
</ul>
@@ -195,7 +197,7 @@ correct JDK to the beginning of your PATH or remove the problematic JDK.</li>
<h3 id="python-version-3">Python version 3</h3>
<p>Repo is built on particular functionality from Python 2.x and is
-unfortunately incompatible with Python 3. In order to use repo, please install
+unfortunately incompatible with Python 3. In order to use repo, please install
Python 2.x:</p>
<pre class="devsite-terminal devsite-click-to-copy">
@@ -212,15 +214,13 @@ You are building on a case-insensitive filesystem.
Please move your source tree to a case-sensitive filesystem.
************************************************************
</pre>
-<p>Please follow the instructions in <a href="initializing.html">Establishing a
-Build Environment</a> for creating a case-sensitive disk image.</p>
+<p>Please follow the instructions in <a href="initializing.html#creating-a-case-sensitive-disk-image">Creating a case-sensitive disk image</a>.</p>
<h3 id="no-usb-permission">No USB permission</h3>
<p>On most Linux systems, unprivileged users cannot access USB ports by
-default. If you see a permission denied error, follow the instructions
-<a href="initializing.html">Initializing the Build Environment</a> for
-configuring USB access.</p>
+default. If you see a permission denied error, follow the instructions in
+<a href="initializing.html#configuring-usb-access">Configuring USB access</a>.</p>
<p>If adb was already running and cannot connect to the device after
getting those rules set up, it can be killed with <code>adb kill-server</code>.