Problems with Android dependencies deserted

The problem is caused by Android dependencies deserted, an Android buddy in the afternoon in the group said recently imported several projects each is Android dependencies error, deserted number, I first said the solution:

Method One: Build your own new project and rebuild the whole project again. perceptibly

Method Two: The Android dependencies item is removed directly, not tested, some say yes, some say the next start still error.

Method Three: Refer to your local appcompat_v7_x Library project,_x is the default generated code, any one can do,

Note Remove the appcompat_v7_x referenced in the original project

The following is a brief explanation of the cause of this problem:

Remember that it was ADT to 22.6. After the 0 release, a new Android project will appear, and the APPCOMPAT_V7 works. and is to create a project new project will appear , particularly griping at everything. Check data said Appcompat_v7 is Google's own compatibility package, is a support library, can let android2.1 above the full use of android4.0 version of the interface. (It was a good thing, but every time a new project was created, it was too griping at everything for the developer, and the working directory was already stretched)

Believe to see here also is not difficult to understand why the above problem, everyone in the uploading or copying works directly to the project copy of the past, are not accustomed to Appcompat_v7 also copied the past, the new import project will be error. Believe this is a griping at everything thing for novice or less careful program apes.

Speaking of which, say something more about it.

What is Android Dependencies?

The official explanation is that Android Dependencies is a virtual folder where Eclipse shows what JAR files, the project depends on. It ' s not a physical folder; You won ' t find it on your hard disk. and the folder is not a checked in to subversion.do not a delete that folder. You'll destroy your project. to fix it, just revert to a older Subversion revision and check it in again.

Just a few words, not clear, simply say: Starting from ADT16, the Android project has a library application folder called "Android Dependencies", which is a new way to refer to ADT third-party libraries. When you need to reference a third-party library, simply create a new folder named "Libs" in your project and copy all third-party packages to that directory. When Eclipse starts, ADT will automatically help you to complete the library reference without having to build the Path yourself as before, and no longer need to referenced libraries.

Here again mentioned Libs , referenced Libraries , we can also think of Android Private Libraries, think down It's not hard to understand the way the library is referenced.

1. Referenced item Set "is Library" tick in "Android" option

2. Reference items in the "Android" option Set "Add" to be referenced

3.android dependencies will display referenced projects, dependent projects

Android Private Libraries: Represents a jar package reference placed inside a libs, considered a private reference

Referenced Libraries: Represents the referenced external jar package.

Other:

If the referenced project and the referenced project are in the same jar package, the version needs to be consistent.

Android Private libraries and referenced libraries cannot repeatedly reference the same jar package, and two of them are sometimes removed.

Recently discovered that the Android Private libraries and referenced libraries can repeatedly reference the same jar package, do not know what to do, and later have time to study again, continue to coding .....

Problems with Android dependencies deserted