Databases
StackOverflow2013
Postsdbo
POCompiling Android .apk on Linux Server
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCompiling Android .apk on Linux Server
    text
    copied!<p>I want to be able to build .apk files programmatically given Android projects (folders, .java, .xml, etc files) with ant on my Ubuntu 10.04 i386 Server. I'm not using Eclipse or even a GUI.</p> <p>1) I have already followed these instructions: <a href="http://source.android.com/source/initializing.html" rel="nofollow">http://source.android.com/source/initializing.html</a></p> <p>2) I downloaded/unpacked the Android Linux SDK here: <a href="http://developer.android.com/sdk/index.html" rel="nofollow">http://developer.android.com/sdk/index.html</a></p> <p>3) Now when I navigate to <code>/home/myusername/www/android-sdk-linux_x86/tools</code> and type in <code>./android</code> I get this error:</p> <pre><code>myusername@myserver:~/www/android-sdk-linux_x86/tools$ ./android Starting Android SDK and AVD Manager No command line parameters provided, launching UI. See 'android --help' for operations from the command line. Exception in thread "main" java.lang.UnsatisfiedLinkError: no swt-pi-gtk-3550 or swt-pi-gtk in swt.library.path, java.library.path or the jar file at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.gtk.OS.&lt;clinit&gt;(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.widgets.Display.&lt;clinit&gt;(Unknown Source) at com.android.sdkmanager.Main.showMainWindow(Main.java:297) at com.android.sdkmanager.Main.doAction(Main.java:281) at com.android.sdkmanager.Main.run(Main.java:99) at com.android.sdkmanager.Main.main(Main.java:88) </code></pre> <p>Any ideas on what is going wrong?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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