first, Import Libar Library project1, the use of third-party library engineering Libary, is basically downloaded from GitHub, after decompression there is a Libary folder 2, the Libary import into Eclipse, the steps as follows 1) in the Eclipse Package Manager, right click on Import, Go to 2) Select the Red section and click Next
3) Import the libary and tick "copy projects into Workspace" (must be checked), click Done
Second, Android engineering reference Libary1. Create a new Android project MyTest
2. Right-click MyTest property
3, the operation is completed, there will be red information error notification
Hint: There are 2 V4 packages found at compile time, there are V4 packages in Libary Library, and V4 packages in MyTest project. Solution:
Right-click on the imported Android Library project file, properties--->java Build Path--->order and Export cancel Android Private Libraries and Android dependencies tick. This will not be exported to the main project. There will be no two android-support-library SHA value inconsistencies when compiling, conflicting issues
4. When you use a class in libary, you are prompted not to find a class or to resolve the solution:
Open the manifest file in libary, set the android:targetsdkversion to match your Android version or higher, then
5, after the above processing, the Android project can be normal use of third-party libary
Iii. Summary1. Imported libary and custom Android items must be in the same workspace and at the same level2. In the libary attribute,cancel the tick of Android Private libraries and Android dependencies3, libary in the inventory file, modifyandroid:targetsdkversion target version consistent or higher with Android project
From for notes (Wiz)
Problems and solutions in the introduction of third-party library engineering in Android projects
