Android sdk manager cannot be started because the swt. jar file is not specified. androidswt. jar

Android sdk manager cannot be started because the swt. jar file is not specified. androidswt. jar

The appearance of this problem actually has nothing to do with the swt. jar file. Finally, the author finds the solution through Baidu at http://www.aichengxu.com/view/39361.

Copy the following content:

Android sdk cannot run or reports "ANDROID_SWT" error. If you need it, refer to it.

After the android sdk is installed, it is generally used in eclise. Once, it was found that the direct running of sdk manager.exe could not be opened and no error was reported. It will disappear in a flash.

Because there is no error message, you have to keep working with eclipse to start sdk manager.

A few days ago, in addition to the official version of android studio, I tried it. As a result, I just installed it and reported an error when I started the configuration. This is better, and an error message "android_swt" is not set.

This error message is very confusing. In fact, it is related to swt, and the methods found on the Internet do not work. It only follows this information and finds that it uses tools \ android. bat to process environment variables.

Therefore, the same error was reported when the bat was run directly. This is easy to do. After reading his content, I found the line with the problem of tools \ lib \ find_java.bat.

"Find/I" x86 "> NUL & set arch_ext = 32 | set arch_ext = 64"

This line indicates that if it is x86, arch_ext = 32 is set; otherwise, it is 64. Used to determine the system version.

It is a pity that there is a problem with this writing method, so that the space followed by the 32 side is also set to the variable.

After removing the spaces followed by 32, the entire batch processing will be normal. ------ I don't know how Google's test was done, so I missed such a serious problem.