Confirmed users
3,990
edits
ReleaseEngineering/Platforms/Android: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Platforms/Android (view source)
Revision as of 20:49, 12 February 2014
, 12 February 2014→Artifacts
| Line 92: | Line 92: | ||
For <b>Android x86</b>, we patched the AOSP "tools_r22" emulator. The original problem was documented in {{bug|917562}}, and we distributed new emulator binaries in {{bug|933918}}. | For <b>Android x86</b>, we patched the AOSP "tools_r22" emulator. The original problem was documented in {{bug|917562}}, and we distributed new emulator binaries in {{bug|933918}}. | ||
== AVD definition == | == AVD definition == | ||
| Line 124: | Line 106: | ||
=== How to generate the AVD definitions === | === How to generate the AVD definitions === | ||
This is the process that graydon followed (the next section shows how to create the same VM that he used): | |||
* Start a new VM (AWS is easiest) running Ubuntu 12.04LTS x86_64 | * Start a new VM (AWS is easiest) running Ubuntu 12.04LTS x86_64 | ||
* Log in | * Log in | ||
| Line 133: | Line 115: | ||
If anything goes wrong in the process (it's quite involved), the easiest solution is probably just to read the source of the script; it contains our best current understanding of how to build AVDs from AOSP sources. It also has quite a lot of options and can restart at particular steps, if part of the build fails. | If anything goes wrong in the process (it's quite involved), the easiest solution is probably just to read the source of the script; it contains our best current understanding of how to build AVDs from AOSP sources. It also has quite a lot of options and can restart at particular steps, if part of the build fails. | ||
=== Create EC2 instance based on graydon's initial AMI === | |||
This will help anyone trying to build the emulator again. | |||
* Go to Amazon's AWS console | |||
* Under EC2's dashboard click on "Images->AMIs" | |||
* Select the "Filter": "Public images" | |||
* Select "N. California" as your zone (us-west-1) | |||
* Search for "ami-d0fcc195" (aka 2014-02-05-android-AVD-builder) | |||
* Select the AMI and launch an instance | |||
* Choose m3.medium | |||
* Select "Next: Configure Instance Details" instead of "Review and Launch" | |||
* Change availability to "us-west-1a" and click on "Review and Launch" | |||
* Click "Launch" | |||
** As key pairs select "Choose an existing key pair" and "aws-releng" | |||
== Deployment of artifacts == | == Deployment of artifacts == | ||