Problem description:
This is a very abnormal problem. It took me more than n time to solve it, and it made me very depressed. This is obviously an ADT bug. Why is the latest version not solved?
When the android project created in Linux is opened in windows, no error is reported. In fact, no errors are reported for all files in the project (with a Red Cross ), however, the project name does have a cross-handed cross, with a picture showing the truth:
Run the command Ctrl + F11 and the following error is returned:
In this case, we should use the clean tool to clean up the binfile of the project and re-generate it, because some resource files may not be compiled after they are added. After clean is used, the problem persists. After n (n> 10) is used, the problem still exists. This is simply a matter of XXX...
No. Try the second method again. The project was not too troublesome, so I just re-built it, So I carefully followed the steps handed over by Google. Unfortunately, the problem persists, then I copied the original project. The problem is that the TMD is still the same. That's all right ~
Some people on the Internet say that clean can be solved without stopping, and others say thatCodeAnd then save it to solve it. Unfortunately, I 've tried all of these issues, but they didn't solve them.
I have never encountered such a problem, and I don't know when it happened. I haven't built an android project in windows for a long time. As a result, I changed my mind. The project I created should be normal. Will it be a problem with eclipse or ADT?
Next, you must know that I updated the ADT and found the solution to the problem when I was about to decompress eclipse again! Goooooooood ~
The original Post website cannot be found, but remember the correct method, that isAdd a variable named android_sdk_home to the system environment variable to point to the root directory of the android SDK.You can, for example:
After adding the variable, restart eclipse.
I don't know why I need to add this environment variable. I have never encountered this problem before, and I haven't updated my components recently. How can this problem suddenly pop up? I don't know. Readers, do you know why? Can you tell me? Thank you!
Reproduced from: http://www.i1987.org /? P = 347