About APPCOMPAT_V7 Bags

No matter how the configuration, there is no way to successfully appcompat_v7 configuration success, and later found a new approach, the original appcompat_v7 is Google's own a Compatibility pack, is a support library, to allow more than 2.1 full use of the 4.0 version of the interface. Therefore, the minimum SDK is chosen directly above Android4.0 No need for this support library.

Reference Links:

appcompat_v7 issues with new ADT when creating a project

Http://jingyan.baidu.com/article/3ea51489e04eb852e61bbaa4.html

1. First solve the project after the completion of the APPCOMPAT_V7 package error. The test package has a red warning issue.

   Click "Project" on the menu bar, select "Clean", then "OK", and when clean is complete, you will find the APPCOMPAT_V7 package error. The problem with the red warning in the test package has been resolved, except that the test package has a yellow warning, just because the import class in Test's Java file is not being used, so it is completely out of control.

   If it does not work, then right-click Appcompat_v7 package, select Properties, click "Android", if the library under the "Is Library" box is not checked, tick, click "OK", then follow the above steps to perform "clean" Operation.

2. After the APPCOMPAT_V7 package is deleted, the test project has various errors, stating that the test project is dependent on the APPCOMPAT_V7 package, so this APPCOMPAT_V7 package cannot be deleted. Then you don't have to take care of the bag, just do your project.

3. If you're still brooding over the appcompat_v7 bag, I'll tell you how to build a project without the APPCOMPAT_V7 package. Since the APPCOMPAT_V7 package is a support library that allows more than 2.1 to use the 4.0 version of the interface, then we have to build the project to select the Minimum SDK above Android4.0 do not need this support library? The result proves that our idea is right.

About APPCOMPAT_V7 Bags