Reputation: 3212
Today, I updated my Android SDK and Eciple ADT to the most recent versions (ADT Rev 22). After restarting Eclipse it is quite unhappy with the Build Paths whenever I reference custom libraries.
An example is shown in this screenshot:
My custom "Android Utilities Library" compiles fine, but everything that depends on it shows build path errors. E.g. when I investigate the build path settings for "Android URA Library" it shows me an error with the android_utilities_library.jar
missing under "Android Dependencies" (which in fact is true, the libraries will be built to individual class files in bin/classes
).
After reading the solution to Build path errors with library projects I tried to clean and manually build my projects in the correct order, but to no avail.
I've never dealt with this before, so I don't know how to attack the problem.
Any help is appreciated. Thx!
Upvotes: 15
Views: 10838
Reputation: 9
if you have import all the Dependencies in your workSpace.maybe you can:projetc-->build all. I meet the problem,and it works well
Upvotes: -1
Reputation: 141
Go to libraries and check the build path of the dependent libraries. It should be same as your projects build path.
Upvotes: 0
Reputation: 3212
Installing the new Build Tools did the trick. They were not automatically included when I updated the SDK (probably need to run the update twice I guess).
Upvotes: 7
Reputation: 1715
I found a solution that works for me: Go to Project Properties > Build Path > Order and Export
Then you have to check each checkbox. In my case my libraries were restored
I hope it will help.
Upvotes: 2
Reputation:
I can see that your project Android URA Library
is referring to Android Utilities Library
, then the problem should not relate to SDK/ADT update.
Please check:
Android URA Library
, choose Project tab and make sure you added Android Utilities Library
as dependency project. Otherwise, please add it.Upvotes: 1