|
1 | 1 | <?xml version="1.0" encoding="UTF-8"?> |
2 | | -<project name="EmailPopup" default="debug"> |
| 2 | +<project name="EmailPopup" default="help"> |
3 | 3 |
|
4 | 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"/> |
| 5 | + It contains the path to the SDK. It should *NOT* be checked into |
| 6 | + Version Control Systems. --> |
| 7 | + <property file="local.properties" /> |
8 | 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. |
| 9 | + <!-- The ant.properties file can be created by you. It is only edited by the |
| 10 | + 'android' tool to add properties to it. |
| 11 | + This is the place to change some Ant specific build properties. |
12 | 12 | Here are some properties you may want to change/update: |
13 | 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'. |
| 14 | + source.dir |
| 15 | + The name of the source directory. Default is 'src'. |
| 16 | + out.dir |
| 17 | + The name of the output directory. Default is 'bin'. |
21 | 18 |
|
22 | | - Properties related to the SDK location or the project target should be updated |
23 | | - using the 'android' tool with the 'update' action. |
| 19 | + For other overridable properties, look at the beginning of the rules |
| 20 | + files in the SDK, at tools/ant/build.xml |
24 | 21 |
|
25 | | - This file is an integral part of the build system for your application and |
26 | | - should be checked in in Version Control Systems. |
| 22 | + Properties related to the SDK location or the project target should |
| 23 | + be updated using the 'android' tool with the 'update' action. |
| 24 | +
|
| 25 | + This file is an integral part of the build system for your |
| 26 | + application and should be checked into Version Control Systems. |
27 | 27 |
|
28 | 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 | | - </path> |
46 | | - |
47 | | - <taskdef name="setup" |
48 | | - classname="com.android.ant.SetupTask" |
49 | | - classpathref="android.antlibs"/> |
50 | | - |
51 | | - <!-- Execute the Android Setup task that will setup some properties specific to the target, |
52 | | - and import the rules files. |
53 | | - To customize the rules, copy/paste them below the task, and disable import by setting |
54 | | - the import attribute to false: |
55 | | - <setup import="false" /> |
56 | | - |
57 | | - This will ensure that the properties are setup correctly but that your customized |
58 | | - targets are used. |
| 29 | + <property file="ant.properties" /> |
| 30 | + |
| 31 | + <!-- if sdk.dir was not set from one of the property file, then |
| 32 | + get it from the ANDROID_HOME env var. |
| 33 | + This must be done before we load project.properties since |
| 34 | + the proguard config can use sdk.dir --> |
| 35 | + <property environment="env" /> |
| 36 | + <condition property="sdk.dir" value="${env.ANDROID_HOME}"> |
| 37 | + <isset property="env.ANDROID_HOME" /> |
| 38 | + </condition> |
| 39 | + |
| 40 | + <!-- The project.properties file is created and updated by the 'android' |
| 41 | + tool, as well as ADT. |
| 42 | +
|
| 43 | + This contains project specific properties such as project target, and library |
| 44 | + dependencies. Lower level build properties are stored in ant.properties |
| 45 | + (or in .classpath for Eclipse projects). |
| 46 | +
|
| 47 | + This file is an integral part of the build system for your |
| 48 | + application and should be checked into Version Control Systems. --> |
| 49 | + <loadproperties srcFile="project.properties" /> |
| 50 | + |
| 51 | + <!-- quick check on sdk.dir --> |
| 52 | + <fail |
| 53 | + message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable." |
| 54 | + unless="sdk.dir" |
| 55 | + /> |
| 56 | + |
| 57 | + <!-- |
| 58 | + Import per project custom build rules if present at the root of the project. |
| 59 | + This is the place to put custom intermediary targets such as: |
| 60 | + -pre-build |
| 61 | + -pre-compile |
| 62 | + -post-compile (This is typically used for code obfuscation. |
| 63 | + Compiled code location: ${out.classes.absolute.dir} |
| 64 | + If this is not done in place, override ${out.dex.input.absolute.dir}) |
| 65 | + -post-package |
| 66 | + -post-build |
| 67 | + -pre-clean |
59 | 68 | --> |
60 | | - <setup /> |
| 69 | + <import file="custom_rules.xml" optional="true" /> |
| 70 | + |
| 71 | + <!-- Import the actual build file. |
61 | 72 |
|
62 | | - <target name="clean"> |
63 | | - <delete dir="${out-folder}" /> |
64 | | - <delete dir="${gen-folder}" /> |
65 | | - </target> |
| 73 | + To customize existing targets, there are two options: |
| 74 | + - Customize only one target: |
| 75 | + - copy/paste the target into this file, *before* the |
| 76 | + <import> task. |
| 77 | + - customize it to your needs. |
| 78 | + - Customize the whole content of build.xml |
| 79 | + - copy/paste the content of the rules files (minus the top node) |
| 80 | + into this file, replacing the <import> task. |
| 81 | + - customize to your needs. |
| 82 | +
|
| 83 | + *********************** |
| 84 | + ****** IMPORTANT ****** |
| 85 | + *********************** |
| 86 | + In all cases you must update the value of version-tag below to read 'custom' instead of an integer, |
| 87 | + in order to avoid having your file be overridden by tools such as "android update project" |
| 88 | + --> |
| 89 | + <!-- version-tag: 1 --> |
| 90 | + <import file="${sdk.dir}/tools/ant/build.xml" /> |
66 | 91 |
|
67 | 92 | </project> |
0 commit comments