Mobile/Fennec/Android/Updating SDK on builders: Difference between revisions

Jump to navigation Jump to search
Line 35: Line 35:
== Downloading tools on non-Linux machines ==
== Downloading tools on non-Linux machines ==
You can't run the `android` binary locally so you'll have to download the tools from the URLs directly:  
You can't run the `android` binary locally so you'll have to download the tools from the URLs directly:  
# Run `android list sdk` - it'll output it the source XML for the various tools it can install. For the primary packages, this is currently located [https://dl.google.com/android/repository/repository-10.xml here].
* Run `android list sdk` - it'll output it the source XML for the various tools it can install. For the primary packages, this is currently located [https://dl.google.com/android/repository/repository-10.xml here].
# Open the url (e.g. `curl <url> | less`) and look through the XML for the tools at the versions you need them. The XML tags follow a pattern:
* Open the url (e.g. `curl <url> | less`) and look through the XML for the tools at the versions you need them. The XML tags follow a pattern:
** Tools: <sdk:tool>
** Tools: <sdk:tool>
** Platform: <sdk:platform>
** Platform: <sdk:platform>
Line 43: Line 43:
** Android Support Library: (separate xml file) <sdk:extra>
** Android Support Library: (separate xml file) <sdk:extra>
** Google Play services: (separate xml file) <sdk:extra>
** Google Play services: (separate xml file) <sdk:extra>
# Look for an <sdk:url> tag. If it's a full url, you're in! Otherwise, guess at the URL based on where you downloaded the SDK and look at some other urls in the file. See the [[#Example URLs|example URLs]].
* Look for an <sdk:url> tag. If it's a full url, you're in! Otherwise, guess at the URL based on where you downloaded the SDK and look at some other urls in the file. See the [[#Example URLs|example URLs]].


=== Example URLs ===
=== Example URLs ===
Confirmed users
975

edits

Navigation menu