Android Project introduces a three-party class library configuration file

Android projects may use a lot of external three-party libraries, such as **.jar or reference a third project, then where do they refer to these things? Let's see.

If the introduction of a three-party jar package, we default is placed in the Libs folder, and we add to build path by adding our classpath, then this action will affect the configuration file is which, the effect is:. Classpath We look at the configuration file content: That's it, we can set it by right-clicking Add to build path in eclipse, assuming that if we don't want to put our package under LIBS, we'll manually configure the Classpath file,  This makes it easy to find our classpath, to be confirmed. The introduction of the three-party project, that is, we right-properties->android->library-> this way to join the three-party project as a library, which is put in which configuration file? Actually it was put on: In the project.properties configuration file, let's look at the following: Target=android-17 android.library.reference.1=. \\autorefreshlistviewandroid.library.reference.2=. \\commontoolsandroid.library.reference.3=. \\chejtandroid.library.reference.4=. \\libraryandroid.library.reference.5=. /idcator_library we've seen this. We've introduced five external projects as an external class library, well, now that we're familiar with a common configuration of project introductions, let's get started.

Android Project introduces a three-party class library configuration file