Android Supported Development Environment Roadmap

by Raphael » Sun, 17 May 2009 12:38:48 GMT


Sponsored Links
 If you all you want is develop for the SDK, at that point any 32-bit
linux distro should be fine. It doesn't have to be Ubuntu. Ubuntu 8.04
and 8.10 should both be fine.

The 64-bit support is still sketchy yet it has been made to work --
that is a 64-bit distro works if you also add some 32-bit packages,
search the android-developers or -beginners forums on the subject.

Whatever linux distro you choose, you'll probably need to install
Eclipse manually (most debian-based distro that I've seen come with a
default Eclipse install that lacks many required plugins.)

For platform development the story should be similar.

Bottom-line: if you just want an easy answer, install ubuntu 8.04
32-bit, install Eclipse for Java developers manually and you're fine.

HTH
R/




--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Dan Stupka » Tue, 19 May 2009 01:12:19 GMT


 hey raphael, your "Bottom'line" is exactly what i was looking for! the only
other piece i'd really appreciate knowing is what's the "next" bottom-line,
e.g. when would it be acceptable/reasonable to use ubuntu 8.10 as "the"
standard os for a team of developers, or ubuntu 9.04? i just want to make
sure that i'm in sync with what's considered the "current" development
environment. also, is there one url that you could point me to as "the"
place for this type of info? many thanks, dls







--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Android Supported Development Environment Roadmap

by Raphael » Tue, 19 May 2009 01:45:30 GMT


 he current bottom line is "go 32-bit". It doesn't really matter
whether you use ubuntu 8.04 or 8.10 or 9.04 or 42.0. Right now the big
limitation is the lack of correct 64-bit support.

To stress it out again: the SDK tools are mostly distro-agnostic. They
don't really rely on the OS much. What they rely on is:
- Java: don't use the default gcj, go for a real jvm from sun and
please use a 32-bit right now.
- ant 1.6+ (for command-line)
- Eclipse Java or RCP (not the crappy default one from ubuntu).

By default ubuntu is not properly configured (it has gcj and the wrong
Eclipse) and no debian-based distro is going to come properly
configured since the correct packages are proprietary. There is an
installation guide on d.android.com and really that's all you need.

HTH
R/

On Mon, May 18, 2009 at 10:11 AM, Dan Stupka <stu...@gmail.com> wrote:

--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Sean Hodges » Tue, 19 May 2009 04:31:54 GMT


 eally? I've been using 64bit OpenJDK6 since the 1.1 SDK came out
without any issues. I wasn't even aware that there was supposed to be
problems!

That's not to say I disagree with Raphael, if 64bit is not supported
then 32bit should be preferred. I'm just a bit surprised at this
comment.


On 5/18/09, Raphael <r...@android.com> wrote:

--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Raphael » Tue, 19 May 2009 04:43:23 GMT


 On Mon, May 18, 2009 at 1:30 PM, Sean Hodges



Lots of people have issues with 64-bit platforms. None of the tools
are ready for it, and if your system accepts 32-bit binaries you're
fine. Plenty of people have made this to work, one way or another.
However the original poster wanted an "easy solution" so I was trying
to not complicate things.

R/

--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Sean Hodges » Tue, 19 May 2009 19:27:59 GMT


 


I'm running Ubuntu 9.04 64bit, I've done nothing to make it support
32bit binaries and the whole SDK runs flawlessly on my machine. That
includes the emulator, SDK tools, ADT plugin in vanilla Eclipse
Ganymede and building against 64bit OpenJDK 6 (from the repositories).
The last time I checked whether 64bit Ubuntu was 32bit binary
compatible out-of-the-box was a few releases ago and it definitely
wasn't, but perhaps things have changed since.

Again, I'm not arguing, just sharing my experiences in case others who
run 64bit systems read this thread.


Fair enough. Dan, you should use 32bit unless you are happy to risk
running into potential issues.

--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Disconnect » Tue, 19 May 2009 19:43:31 GMT


 "file {sdk}/tools/emulator" will reveal that you are running a bunch of
32-bit binaries.






--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Sean Hodges » Tue, 19 May 2009 20:04:46 GMT


 Thanks disconnect, I didn't think to check the ELF headers, although I
was fairly certain that the SDK I downloaded was 32bit anyway. It does
confirm that I'm running the 32bit binaries in an unmodified 64bit
Ubuntu environment.






--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Xavier Ducrohet » Wed, 20 May 2009 04:21:53 GMT


 I'll add to this that the only issue with 64bit is for the standalone
SWT-based tools: DDMS and Traceview.

If you don't use Traceview, and use DDMS from within Eclipse with ADT,
then you will probably be fine.

Xav







-- 
Xavier Ducrohet
Android Developer Tools Engineer
Google Inc.

--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Fred Grott » Wed, 20 May 2009 04:27:18 GMT


 Sounds like the swt support for 64-bit is the bottleneck..have not switched
myself yet

Of course the original thread author could use a VM such as Virtual Box to
run 32-bit inside of 64-bit to work around that if they wanted although that
is probably not the only work-around







--~--~---------~--~----~------------~-------~--~----~



Android Supported Development Environment Roadmap

by Dan Stupka » Fri, 29 May 2009 07:17:52 GMT


 i really appreciate all the great feedback! sorry for the late reply... many
thanks to all, dls









--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. How To Disconnect a Bluetooth Device With The HOME Button

My application connects to multiple bluetooth devices. I want to stop the 
connection whenever the user leaves the app, including when they press the 
HOME button. However I have no way of detecting when HOME is pressed, which 
will keep the bluetooth connection running, thus continuing to drain the 
battery of the phone. All of the examples I've found, including the ones in 
the Android Developer site, do not take care of disconnecting when leaving 
the app.

I can check to see if the user completely backs out of the application using 
the BACK button, but not the HOME. Is there a way that I can accomplish this 
without having to wait for the phone to decide it needs more memory and then 
destroy the activity?

-- 

2. Two activities in one window

Hi,

I'm developing an application where the users can modify the internet
access point settings, but because the apn settings are secure
settings they can't be changed programmatically. So what I would like
to do is to open the apn settings activity and in the same window show
the values that the user should input to the settings. I have been
trying to look the ActivityGroup API but couldn't figure out if this
is possible to do with that. Anyone have any ideas how to show two
activities (one with the setting values, and another one where to
input the values) in the same window so the user doesn't have to
switch between activities?? Or any other ideas how the user could
modify the secure settings easily?

-Mika

-- 

3. Resuming Previous Activity Properly

4. modifying build.prop on emulator

5. Sharing gps stuff between several activity

6. Record the Output audio from device

7. EditText View control distorted in a qvga android phone as well as the emulator