| 1 |
<?xml version="1.0" encoding="UTF-8"?> |
| 2 |
<project name="AndroidUtils" default="help"> |
| 3 |
|
| 4 |
<!-- The local.properties file is created and updated by the 'android' tool. |
| 5 |
It contains the path to the SDK. It should *NOT* be checked into |
| 6 |
Version Control Systems. --> |
| 7 |
<!--loadproperties srcFile="local.properties" /--> |
| 8 |
|
| 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 |
Here are some properties you may want to change/update: |
| 13 |
|
| 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'. |
| 18 |
|
| 19 |
For other overridable properties, look at the beginning of the rules |
| 20 |
files in the SDK, at tools/ant/build.xml |
| 21 |
|
| 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 |
|
| 28 |
--> |
| 29 |
<property file="ant.properties" /> |
| 30 |
|
| 31 |
|
| 32 |
<!-- The project.properties file is created and updated by the 'android' |
| 33 |
tool, as well as ADT. |
| 34 |
|
| 35 |
This contains project specific properties such as project target, and library |
| 36 |
dependencies. Lower level build properties are stored in ant.properties |
| 37 |
(or in .classpath for Eclipse projects). |
| 38 |
|
| 39 |
This file is an integral part of the build system for your |
| 40 |
application and should be checked into Version Control Systems. --> |
| 41 |
<loadproperties srcFile="project.properties" /> |
| 42 |
|
| 43 |
<!-- quick check on sdk.dir --> |
| 44 |
<fail |
| 45 |
message="sdk.dir is missing. Make sure to generate local.properties using 'android update project'" |
| 46 |
unless="sdk.dir" |
| 47 |
/> |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
<!-- extension targets. Uncomment the ones where you want to do custom work |
| 52 |
in between standard targets --> |
| 53 |
<!-- |
| 54 |
<target name="-pre-build"> |
| 55 |
</target> |
| 56 |
<target name="-pre-compile"> |
| 57 |
</target> |
| 58 |
|
| 59 |
/* This is typically used for code obfuscation. |
| 60 |
Compiled code location: ${out.classes.absolute.dir} |
| 61 |
If this is not done in place, override ${out.dex.input.absolute.dir} */ |
| 62 |
<target name="-post-compile"> |
| 63 |
</target> |
| 64 |
--> |
| 65 |
|
| 66 |
<!-- Import the actual build file. |
| 67 |
|
| 68 |
To customize existing targets, there are two options: |
| 69 |
- Customize only one target: |
| 70 |
- copy/paste the target into this file, *before* the |
| 71 |
<import> task. |
| 72 |
- customize it to your needs. |
| 73 |
- Customize the whole content of build.xml |
| 74 |
- copy/paste the content of the rules files (minus the top node) |
| 75 |
into this file, replacing the <import> task. |
| 76 |
- customize to your needs. |
| 77 |
|
| 78 |
*********************** |
| 79 |
****** IMPORTANT ****** |
| 80 |
*********************** |
| 81 |
In all cases you must update the value of version-tag below to read 'custom' instead of an integer, |
| 82 |
in order to avoid having your file be overridden by tools such as "android update project" |
| 83 |
--> |
| 84 |
<!-- version-tag: 1 --> |
| 85 |
<import file="${sdk.dir}/tools/ant/build.xml" /> |
| 86 |
|
| 87 |
</project> |
Parent Directory
| 
Revision Log