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 On Mon, May 18, 2009 at 6:18 PM, Xavier Ducrohet <[email protected]> wrote: > > 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 > > On Mon, May 18, 2009 at 1:42 PM, Raphael <[email protected]> wrote: > > > > On Mon, May 18, 2009 at 1:30 PM, Sean Hodges > > <[email protected]> wrote: > >> > >> Really? 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! > > > > 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/ > > > > > > > > > > > -- > Xavier Ducrohet > Android Developer Tools Engineer > Google Inc. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
