summaryrefslogtreecommitdiff
path: root/static
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2019-08-09 09:39:33 -0400
committerDaniel Micay <danielmicay@gmail.com>2019-08-09 09:39:33 -0400
commitcc434437747db1e84c7d87d9483272c32e73f4d2 (patch)
tree3785bd72b85f803045993743729671d2f868f701 /static
parentec19c894c49b808878c1a39d827c6b67a8a21c6b (diff)
expand standalone SDK documentation
Diffstat (limited to 'static')
-rw-r--r--static/build.html16
1 files changed, 11 insertions, 5 deletions
diff --git a/static/build.html b/static/build.html
index b36407c2..6833eee3 100644
--- a/static/build.html
+++ b/static/build.html
@@ -574,12 +574,18 @@ cd ../..</pre>
</h2>
<p>It can be useful to set up a standalone installation of the SDK separate from
- Android Studio. Android Studio can also be set up to use an existing SDK and will
- recognize it and use it automatically if Android Studio is installed with an SDK
- installation already available and set up in the environment. You'll also likely want
- a working command-line SDK environment even if you do heavily use Android Studio.</p>
+ the Android Open Source Project tree. This is how the prebuilt apps are built, rather
+ than using the older branch of the SDK in the OS source tree.</p>
- <p>To set up a minimal SDK installation without Android Studio on Linux:</p>
+ <p>Android Studio can also be set up to use an existing SDK and will recognize it and use
+ it automatically if Android Studio is installed with an SDK installation already
+ available and set up in the environment. You'll also likely want a working
+ command-line SDK environment even if you do heavily use Android Studio.</p>
+
+ <p>Using the official releases of the SDK is recommended for simplicity, although with
+ a lot of effort you can build everything yourself. Distribution packages are generally
+ quite out-of-date and should be avoided. To set up a minimal SDK installation without
+ Android Studio on Linux:</p>
<pre>mkdir ~/sdk
cd ~/sdk