expand standalone SDK documentation
This commit is contained in:
parent
ec19c894c4
commit
cc43443774
@ -574,12 +574,18 @@ cd ../..</pre>
|
|||||||
</h2>
|
</h2>
|
||||||
|
|
||||||
<p>It can be useful to set up a standalone installation of the SDK separate from
|
<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
|
the Android Open Source Project tree. This is how the prebuilt apps are built, rather
|
||||||
recognize it and use it automatically if Android Studio is installed with an SDK
|
than using the older branch of the SDK in the OS source tree.</p>
|
||||||
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>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
|
<pre>mkdir ~/sdk
|
||||||
cd ~/sdk
|
cd ~/sdk
|
||||||
|
Loading…
x
Reference in New Issue
Block a user