Mercurial > MadButterfly
comparison Android/examples/testpath/build.xml @ 501:e505597c17fb Android_Skia
testpath is an Android Java application for demo MadButterfly.
| author | Thinker K.F. Li <thinker@branda.to> |
|---|---|
| date | Tue, 01 Dec 2009 22:55:08 +0800 |
| parents | |
| children | 47c6fd9dd83c |
comparison
equal
deleted
inserted
replaced
| 500:f06eba21db1c | 501:e505597c17fb |
|---|---|
| 1 <?xml version="1.0" encoding="UTF-8"?> | |
| 2 <project name="testpath" default="help"> | |
| 3 | |
| 4 <!-- The local.properties file is created and updated by the 'android' tool. | |
| 5 It contain the path to the SDK. It should *NOT* be checked in in Version | |
| 6 Control Systems. --> | |
| 7 <property file="local.properties"/> | |
| 8 | |
| 9 <!-- The build.properties file can be created by you and is never touched | |
| 10 by the 'android' tool. This is the place to change some of the default property values | |
| 11 used by the Ant rules. | |
| 12 Here are some properties you may want to change/update: | |
| 13 | |
| 14 application-package | |
| 15 the name of your application package as defined in the manifest. Used by the | |
| 16 'uninstall' rule. | |
| 17 source-folder | |
| 18 the name of the source folder. Default is 'src'. | |
| 19 out-folder | |
| 20 the name of the output folder. Default is 'bin'. | |
| 21 | |
| 22 Properties related to the SDK location or the project target should be updated | |
| 23 using the 'android' tool with the 'update' action. | |
| 24 | |
| 25 This file is an integral part of the build system for your application and | |
| 26 should be checked in in Version Control Systems. | |
| 27 | |
| 28 --> | |
| 29 <property file="build.properties"/> | |
| 30 | |
| 31 <!-- The default.properties file is created and updated by the 'android' tool, as well | |
| 32 as ADT. | |
| 33 This file is an integral part of the build system for your application and | |
| 34 should be checked in in Version Control Systems. --> | |
| 35 <property file="default.properties"/> | |
| 36 | |
| 37 <!-- Custom Android task to deal with the project target, and import the proper rules. | |
| 38 This requires ant 1.6.0 or above. --> | |
| 39 <path id="android.antlibs"> | |
| 40 <pathelement path="${sdk-location}/tools/lib/anttasks.jar" /> | |
| 41 <pathelement path="${sdk-location}/tools/lib/sdklib.jar" /> | |
| 42 <pathelement path="${sdk-location}/tools/lib/androidprefs.jar" /> | |
| 43 <pathelement path="${sdk-location}/tools/lib/apkbuilder.jar" /> | |
| 44 <pathelement path="${sdk-location}/tools/lib/jarutils.jar" /> | |
| 45 <pathelement path="${sdk-location}/tools/lib/mbfly-java.jar" /> | |
| 46 </path> | |
| 47 | |
| 48 <taskdef name="setup" | |
| 49 classname="com.android.ant.SetupTask" | |
| 50 classpathref="android.antlibs"/> | |
| 51 | |
| 52 <!-- Execute the Android Setup task that will setup some properties specific to the target, | |
| 53 and import the build rules files. | |
| 54 | |
| 55 The rules file is imported from | |
| 56 <SDK>/platforms/<target_platform>/templates/android_rules.xml | |
| 57 | |
| 58 To customize some build steps for your project: | |
| 59 - copy the content of the main node <project> from android_rules.xml | |
| 60 - paste it in this build.xml below the <setup /> task. | |
| 61 - disable the import by changing the setup task below to <setup import="false" /> | |
| 62 | |
| 63 This will ensure that the properties are setup correctly but that your customized | |
| 64 build steps are used. | |
| 65 --> | |
| 66 <setup /> | |
| 67 </project> |