Android SDK Setup under Windows 7 Pro 64 bit

Question

The short version of my issue at hand,

• Windows 7 Professional x64
• Java JDK 1.6.0_17 x64
• Eclipse Galileo w\ADT Plugin installed
• Android SDKtools r04

Since the Android SDK download now only includes the tools, you have to run the included SDK Manager application (SDK Setup) through which you can download the platforms, additional tools, docs,etc.

Under my current configuration SDK Setup bombs on launch, so, I can't do anything since I do not have a single platform to start writing against...I've read a few places that the fix is "just install the 32 bit JDK and all will be well" that seems surprising and disappointing option for a work around(downloading it now to try).

My question is this, anyone else run into this same issue and how did you get past it? Is there a place I can "download by hand" the components I need that I missed on the Android SDK site?

Odds are pretty good that the 32 bit "fix" will work, but that seems wrong that I'll have to install a secondary version of the same SDK/JRE just to run this tool and to download the actual Android SDK components

Thanks!

UPDATE: Well, the work around that requires you to also install 32 bit java and referencing that as your JAVA_HOME worked, either by calling the SDK setup manually or through eclipse. I'm not particularly happy with that, so I'll leave this one open for the time being in case there are other ways to get this done that people may know about.

UPDATE 2: Not directly related since it is Linux centric, but there are troubleshooting steps if trying to run the SDK/Eclipse under Linux 64bit where they reference the need to be able to run 32 bit, but nothing similar under windows x64

FINAL UPDATE (?) Taking the info Seth's answer gave me, and running the bat manually(once I knew what file SDK Setup was running) the answer for me was simply adding ANDROID_SWT path variable that pointed to a valid location with the x86_64 swt.jar....the android sdk directory had one, seemingly in the right place, but it couldn't find it until I added that to my path.

Thanks All!

Answer 1

I initially had this problem and I believe it was because I did not have the 64 bit version of Eclipse.

Answer 2

If SDK Setup.exe fails, please try to open a command-prompt and run "tools\android.bat" manually. That's all what SDK Setup does, however the current version has a bug in that it doesn't display errors that the batch might output:

 > cd <your-sdk>\tools
 > android.bat

That way you may see a more useful error message.

You must have a java.exe on your %PATH%.

Answer 3

Windows 7 isn't a supported platform as far as I know. I use the SDK on 64-bit Ubuntu 9.10 and it works fine, though I did have to install the ia32libs or libcurses bombed every time. That was Eclipse related.

The SDK sys reqs makes it clear whatever platform you run, you must be able to run 32-bit code.

Answer 4

To answer your question about downloading files by hand, you can extract the relevant URLs from the SDK Manager's repository manifest:

https://dl-ssl.google.com/android/repository/repository.xml

Answer 5

Found a solution that modifies the android.bat to allow you to start and run the android sdk and avd manager on the x64 jdk. So far I've been able to start it updating, but I don't know what other implications running the emulator and compiling against the x64 jdk will have.

http://code.google.com/p/android/issues/detail?id=3917

good luck.

Answer 6

I managed to run the SDK Setup by adding the location of the Java JDK to the system path. so far so good.

Answer 7

My problem was installing the Android SDK in Eclipse Helios on Windows 7 Enterprise 64bit, I was getting the following error:

Missing requirement: Android Development Tools 0.9.7.v201005071157-36220 (com.android.ide.eclipse.adt.feature.group 0.9.7.v201005071157-36220) requires 'org.eclipse.jdt.junit 0.0.0' but it could not be found

Having followed the advice above to ensure that the JDK was in my PATH variable (it wasn't), installation went smoothly. I guess the error was somewhat spurious (incidentally if you're looking for the JARs that correspond to that class, they were in my profile rather than the Eclipse installation directory)

So, check that PATH variable!