1 <?xml version="1.0" encoding="UTF-8"?> 2 <project name="testproject" default="help"> 3 4 <!-- The local.properties file is created and updated by the 'android' 5 tool. 6 It contains the path to the SDK. It should *NOT* be checked into 7 Version Control Systems. --> 8 <property file="local.properties" /> 9 10 <!-- The build.properties file can be created by you and is never touched 11 by the 'android' tool. This is the place to change some of the 12 default property values used by the Ant rules. 13 Here are some properties you may want to change/update: 14 15 source.dir 16 The name of the source directory. Default is 'src'. 17 out.dir 18 The name of the output directory. Default is 'bin'. 19 20 Properties related to the SDK location or the project target should 21 be updated using the 'android' tool with the 'update' action. 22 23 This file is an integral part of the build system for your 24 application and should be checked into Version Control Systems. 25 26 --> 27 <property file="build.properties" /> 28 29 <!-- The default.properties file is created and updated by the 'android' 30 tool, as well as ADT. 31 This file is an integral part of the build system for your 32 application and should be checked into Version Control Systems. --> 33 <property file="default.properties" /> 34 35 36 <!-- Required pre-setup import --> 37 <import file="${sdk.dir}/tools/ant/pre_setup.xml" /> 38 39 40 <!-- extension targets. Uncomment the ones where you want to do custom work 41 in between standard targets --> 42 <!-- 43 <target name="-pre-build"> 44 </target> 45 <target name="-pre-compile"> 46 </target> 47 48 [This is typically used for code obfuscation. 49 Compiled code location: ${out.classes.absolute.dir} 50 If this is not done in place, override ${out.dex.input.absolute.dir}] 51 <target name="-post-compile"> 52 </target> 53 --> 54 55 <!-- Execute the Android Setup task that will setup some properties 56 specific to the target, and import the build rules files. 57 58 The rules file is imported from 59 <SDK>/tools/ant/ 60 Depending on the project type it can be either: 61 - main_rules.xml 62 - lib_rules.xml 63 - test_rules.xml 64 65 To customize existing targets, there are two options: 66 - Customize only one target: 67 - copy/paste the target into this file, *before* the 68 <setup> task. 69 - customize it to your needs. 70 - Customize the whole script. 71 - copy/paste the content of the rules files (minus the top node) 72 into this file, *after* the <setup> task 73 - disable the import of the rules by changing the setup task 74 below to <setup import="false" />. 75 - customize to your needs. 76 --> 77 <setup /> 78 79 </project> 80
