Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I just ran into the same problem. I found a workaround though.</p> <p>The first one is a cop-out: Download the platforms on a headed system and simply copy the platform subdirectories into your android sdk/platforms dir.</p> <p>If, like me, you don't have immediate access to another headed android dev environment, you can go to Google's SDK archives and download one of the other SDK's that included the platforms. This way means that you can only develop for Android 1.1 and 1.5 though.</p> <p>The download to get for linux systems is their Android 1.5 r3. Of course, google's sdk download pages aren't lynx-friendly, so I had to get the direct link from another GUI system.</p> <pre><code>wget http://dl.google.com/android/archives/android-sdk-linux_x86-1.5_r3.zip </code></pre> <p>Then it's simply a matter of unzipping the archive, and moving the platform sibdirs to your newer SDK platform dir.</p> <pre><code>android create avd -t 3 -p path/to/avd/dir -n "name" </code></pre> <p>This creates an AVD for the 1.5 platform with your specified name and directory. Note that the avd dir shouldn't exist. If you want to overwrite, add --force to the command.</p> <p>Getting this far has a platform installed and creates an AVD. Unfortunately, trying to build failed at this point for me because I run a 64bit server, and google only releases 32bit tools.</p> <p>I found a solution for this in the accepted answer of <a href="https://stackoverflow.com/questions/1943746/android-eclipse-plugin-cant-find-valid-paths">this stackoverflow question</a> and used <code>sudo apt-get install ia32-libs</code> to enable the ability to run the 32bit tools.</p> <p>Then you should be able to use the android tool on the CLI to either convert an eclipse project (for 1.5 or lower) to have an ant build system, or you can have it create a new project for you to start working on.</p> <p>Hope this helps!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload