Hey guys, the issue at hand now is the SDK/android.bat does not locate the SWT file.
I'm running Windows 7 x64, my file locations are as follows:
Android SDK (zip version) - C:\android-sdk-windows
SWT.jar (from the Zip) - C:\android-sdk-windows\tools\lib\ --- in these folders -->(x86)32bit and (x86_64)64bit
JDK 6u24 x64 - C:\Program Files\Java\jdk1.6.0_24
My environment variables are as follows:
ANDROID_SWT = C:\android-sdk-windows\tools\lib\x86_64
Path = ;C:\Program Files\Java\jdk1.6.0_24\bin
Ok, now then, i was able to get java running thanks to Alpine but that led me to the following issue.
Upon execution of the Android SDK manager, a black command screen quickly flashes and disseapears, it doesn't start the SDK therefore i cannot download any of the platforms nor add-ons.
-Note that i have those files already from the zip (platforms and ad-ons)-
I've traced the culprit to the android.bat file but can't seem to figure it out. I've set the environment variable for the SWT.jar file. I didn't modify the .bat file in any way so far.
The following is my bat file and the error is located near the bottom. @echo off rem Copyright (C) 2007 The Android Open Source Project rem rem Licensed under the Apache License, Version 2.0 (the "License"); rem you may not use this file except in compliance with the License. rem You may obtain a copy of the License at rem rem http://www.apache.org/licenses/LICENSE-2.0
rem rem Unless required by applicable law or agreed to in writing, software rem distributed under the License is distributed on an "AS IS" BASIS, rem WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. rem See the License for the specific language governing permissions and rem limitations under the License.
rem Useful links: rem Command-line reference: rem http://technet.microsoft.com/en-us/l.../bb490890.aspx
rem don't modify the caller's environment setlocal
rem Set up prog to be the path of this script, including following symlinks, rem and set up progdir to be the fully-qualified pathname of its directory. set prog=%~f0
rem Grab current directory before we change it set work_dir="%cd%"
rem Change current directory and drive to where the script is, to avoid rem issues with directories containing whitespaces. cd /d %~dp0
rem Check we have a valid Java.exe in the path. set java_exe= call lib\find_java.bat if not defined java_exe goto :EOF
rem Set SWT.Jar path based on current architecture (x86 or x86_64) for /f %%a in ('%java_exe% -jar lib\archquery.jar') do set swt_path=lib\%%a
if "%1 %2"=="update sdk" goto StartUi if not "%1"=="" goto EndTempCopy :StartUi echo [INFO] Starting Android SDK and AVD Manager
rem We're now going to create a temp dir to hold all the Jar files needed
rem to run the android tool, copy them in the temp dir and finally execute
rem from that path. We do this only when the launcher is run without
rem arguments, to display the SDK Updater UI. This allows the updater to
rem update the tools directory where the updater itself is located.
xcopy %swt_path% %tmp_dir%\%swt_path% /I /E /C /G /R /Y /Q > nul
copy /B /D /Y lib\androidprefs.jar %tmp_dir%\lib\ > nul
copy /B /D /Y lib\org.eclipse.* %tmp_dir%\lib\ > nul
copy /B /D /Y lib\sdk* %tmp_dir%\lib\ > nul
copy /B /D /Y lib\common.jar %tmp_dir%\lib\ > nul
copy /B /D /Y lib\commons-compress* %tmp_dir%\lib\ > nul
rem jar_path and swt_path are relative to PWD so we don't need to adjust them, just change dirs.
cd /d %tmp_dir%
rem The global ANDROID_SWT always override the SWT.Jar path if defined ANDROID_SWT set swt_path=%ANDROID_SWT%
if exist %swt_path% goto SetPath echo ERROR: SWT folder '%swt_path%' does not exist. echo Please set ANDROID_SWT to point to the folder containing swt.jar for your platform. goto :EOF
:SetPath rem Finally exec the java program and end here. call %java_exe% -Dcom.android.sdkmanager.toolsdir="%tools_dir%" -Dcom.android.sdkmanager.workdir=%work_dir% -classpath "%jar_path%;%swt_path%\swt.jar" com.android.sdkmanager.Main %*
This is what i get upon executing the bat file via command prompt
C:\Users\MuniFC Portable11>C:\android-sdk-windows\tools\android.bat [INFO] Starting Android SDK and AVD Manager 'xcopy' is not recognized as an internal or external command, operable program or batch file. No command line parameters provided, launching UI. See 'android --help' for operations from the command line. java.lang.NullPointerException at com.android.sdklib.internal.avd.AvdManager.parseAv dInfo(AvdManager.ja va:1205) at com.android.sdklib.internal.avd.AvdManager.buildAv dList(AvdManager.ja va:1184) at com.android.sdklib.internal.avd.AvdManager.<init>( AvdManager.java:385 ) at com.android.sdkuilib.internal.repository.UpdaterDa ta.initSdk(UpdaterD ata.java:238) at com.android.sdkuilib.internal.repository.UpdaterDa ta.<init>(UpdaterDa ta.java:114) at com.android.sdkuilib.internal.repository.UpdaterWi ndowImpl.<init>(Upd aterWindowImpl.java:86) at com.android.sdkuilib.repository.UpdaterWindow.<ini t>(UpdaterWindow.ja va:42) at com.android.sdkmanager.Main.showMainWindow(Main.ja va:302) 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)
If you have any idea on how to fix this that would be awesome!