Http://www.cnblogs.com/shortboy/p/4424944.html
Prologue: In fact, this article is a bit wasted.
Detailed description is: Http://blog.csdn.net/qiujuer/article/details/39754517?utm_source=tuicool
1. (*.aar) is almost something from Android studio, so you'll want to use Eclipse for Android studio based on "IntelliJ idea" and you need to know what's inside of this thing!
2. Say 10,000 steps back, since Android Studio uses (*.aar), you have to learn to use Android Studio, why use Eclipse to get this (*.aar)?
3. What? Because GitHub's open source projects build projects with "Gradle" to rely on these packages (*.aar).
4. While Android Studio was originally using Gradle, the direct GitHub URL was imported and took two minutes to run the project.
Hey, there's no way. It seems that eclipse didn't know what to do. (If you have a new Android project, it's highly recommended to use Android Studio, after all, it's true that Daniel on GitHub is using Gradle, not to mention Android studio.)
If you're looking for trouble using Eclipse's (*.aar) package, go ahead and look at the spit slots above.
Premise: I assume that the package (*.aar) is obtained from the V4 or V7 in "%android_home%\extras\android\m2repository".
What the? Your SDK has not been updated to the "M2repository" folder or "blocked by the big Celestial network cannot be updated."
All right! You win, you go see http://www.cnblogs.com/shortboy/archive/2012/10/25/2738294.html this article.
Update your SDK and come back to see it.
(In fact, when I was not using Android studio, it was not updated to the "M2repository" folder when I was developing the eclipse)
When the update is complete
Anyway
1. Let's take appcompat-v7 for example, what do you not know appcompat-v7 have?
Take a look at this article: http://blog.csdn.net/xyz_lmn/article/details/12623609
2. We see the following picture of the file, we see the Sir (*.arr) file
3. Let's just double-click to see what's inside?
, there is a jar, and other similar working directories in Eclipse, such as res,assets,androidmanifest.xml these files
4. If so, can we consider when this (*.arr) Res,assets,androidmanifest.xml is a file in Eclipse Android Libs project, copy the past and then declare the project as Libs
5. Then import your Class.jar in the project you want to use (of course, you need to change it to the corresponding name, if you do not change I can not resist you how)
6. Now you re-introduce the Libs project and start your project again. (If you do not introduce the Libs project, it is estimated that you will not find an exception for a resource if you add only the jar).
After these six steps, you also feel that using Eclipse to guide (*.arr) use no trouble. I can only say. You win. Bye
How to use (*.aar) files in Android Eclipse development