ah yeah that's a problem.
It looks like we removed this enforcing of 1.5 from the DDMS/Traceview
but we forgot to remove it from android.
We're going to fix this, but in the mean time you can either reorder
your java priorities as Chris said, or you can replace the line 69 in
tools/android:
java_cmd="/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Commands/java"
by
java_cmd="java"
Xav
On Wed, Oct 28, 2009 at 4:23 PM, Chris Garman <[email protected]> wrote:
>
> I had the same problem as the original poster. It looks like my
> access rights were all correct.
>
> Here's a theory though. Check your Java Preferences (Applications-
>>Utilities->Java Preferences) to see which is the preferred order of
> Java for your Java Applications. Initially my ordering was this: Java
> 6 (64-bit), Java 5 (64-bit), Java 5 (32-bit), Java 1.4.2 (32-bit). In
> the android script, it explicitly calls to the 1.5 version of java,
> which, given my preferences, ran the 64-bit version of Java 5. So
> the android script explicitly calls Java 5, to avoid running in 64-bit
> mode, but the preferences dictate to use the 64-bit version of Java 5,
> and thus it does.
>
> Here's the snippet from tools/android:
> # Mac OS X needs an additional arg, or you get an "illegal thread"
> complaint.
> if [ `uname` = "Darwin" ]; then
> os_opts="-XstartOnFirstThread"
> #because Java 1.6 is 64 bits only and SWT doesn't support this, we
> force the usage of java 1.5
> java_cmd="/System/Library/Frameworks/JavaVM.framework/Versions/1.5/
> Commands/java"
> .....
>
> Initially changing java_cmd from "/System/Library/Frameworks/
> JavaVM.framework/Versions/1.5/Commands/java" to "java" worked for me
> (so this switched from 1.5 (64-bit) to 1.6(64-bit). I played with a
> few combinations and here are my results:
>
> Java 1.6 (64-bit) - works
> Java 1.5 (64-bit) - does not work
> Java 1.5 (32-bit) - works
>
> So my guess is that you need the right combination of java_cmd in the
> android script and Java Preferences to get it to work correctly.
>
>
> On Oct 28, 1:34 pm, Xavier Ducrohet <[email protected]> wrote:
>> This really shouldn't be necessary. Can you check the access rights on
>> the files you extracted?
>>
>> Xav
>>
>>
>>
>>
>>
>> On Tue, Oct 27, 2009 at 3:20 PM, fern <[email protected]> wrote:
>>
>> > I just did this:
>>
>> > 1) download sdk (android-sdk_r3-mac.zip)
>> > (good so far)
>> > 2) extract sdk (unzip android-sdk_r3-mac.zip)
>> > (yup, extracts all fine and dandy)
>> > 3) add sdk to path (export ANDROID_SDK_HOME, export PATH=${PATH}:$
>> > {ANDROID_SDK_HOME}/tools )
>> > (ok, I can now execute any command, android, adb, etc)
>>
>> > 4) try to run "android udpate sdk" as the Readme.txt says to:
>>
>> > android update sdk
>> > No command line parameters provided, launching UI.
>> > See 'android --help' for operations from the command line.
>>
>> > But nothing. The UI doesn't come up. Nothing happens. But then, if
>> > I run it with sudo, it now launches the UI. What's going on? Can I
>> > please fix this, I don't want to run everything with sudo.
>>
>> > sudo android update sdk
>> > No command line parameters provided, launching UI.
>> > See 'android --help' for operations from the command line.
>> > --- NOW THE UI POPS UP ---
>>
>> --
>> Xavier Ducrohet
>> Android SDK Tech Lead
>> Google Inc.
>>
>> Please do not send me questions directly. Thanks!
>
> >
>
--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
Please do not send me questions directly. Thanks!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Beginners" 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-beginners?hl=en
-~----------~----~----~----~------~----~------~--~---
