update build.xml

This commit is contained in:
Mathieu Maret 2011-11-17 15:22:28 +01:00
parent dbe3c9b13f
commit 14bd9ff3b4

View File

@ -1,15 +1,14 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<project name="MultiSmsSender" default="help"> <project name="MultiSmsSender" default="help">
<!-- The local.properties file is created and updated by the 'android' <!-- The local.properties file is created and updated by the 'android' tool.
tool.
It contains the path to the SDK. It should *NOT* be checked into It contains the path to the SDK. It should *NOT* be checked into
Version Control Systems. --> Version Control Systems. -->
<property file="local.properties" /> <loadproperties srcFile="local.properties" />
<!-- The build.properties file can be created by you and is never touched <!-- The ant.properties file can be created by you. It is only edited by the
by the 'android' tool. This is the place to change some of the 'android' tool to add properties to it.
default property values used by the Ant rules. This is the place to change some Ant specific build properties.
Here are some properties you may want to change/update: Here are some properties you may want to change/update:
source.dir source.dir
@ -17,6 +16,9 @@
out.dir out.dir
The name of the output directory. Default is 'bin'. The name of the output directory. Default is 'bin'.
For other overridable properties, look at the beginning of the rules
files in the SDK, at tools/ant/build.xml
Properties related to the SDK location or the project target should Properties related to the SDK location or the project target should
be updated using the 'android' tool with the 'update' action. be updated using the 'android' tool with the 'update' action.
@ -24,26 +26,25 @@
application and should be checked into Version Control Systems. application and should be checked into Version Control Systems.
--> -->
<property file="build.properties" /> <property file="ant.properties" />
<!-- The default.properties file is created and updated by the 'android' <!-- The project.properties file is created and updated by the 'android'
tool, as well as ADT. tool, as well as ADT.
This contains project specific properties such as project target, and library
dependencies. Lower level build properties are stored in ant.properties
(or in .classpath for Eclipse projects).
This file is an integral part of the build system for your This file is an integral part of the build system for your
application and should be checked into Version Control Systems. --> application and should be checked into Version Control Systems. -->
<property file="default.properties" /> <loadproperties srcFile="project.properties" />
<!-- Custom Android task to deal with the project target, and import the <!-- quick check on sdk.dir -->
proper rules. <fail
This requires ant 1.6.0 or above. --> message="sdk.dir is missing. Make sure to generate local.properties using 'android update project'"
<path id="android.antlibs"> unless="sdk.dir"
<pathelement path="${sdk.dir}/tools/lib/anttasks.jar" /> />
<pathelement path="${sdk.dir}/tools/lib/sdklib.jar" />
<pathelement path="${sdk.dir}/tools/lib/androidprefs.jar" />
</path>
<taskdef name="setup"
classname="com.android.ant.SetupTask"
classpathref="android.antlibs" />
<!-- extension targets. Uncomment the ones where you want to do custom work <!-- extension targets. Uncomment the ones where you want to do custom work
in between standard targets --> in between standard targets -->
@ -53,32 +54,32 @@
<target name="-pre-compile"> <target name="-pre-compile">
</target> </target>
[This is typically used for code obfuscation. /* This is typically used for code obfuscation.
Compiled code location: ${out.classes.absolute.dir} Compiled code location: ${out.classes.absolute.dir}
If this is not done in place, override ${out.dex.input.absolute.dir}] If this is not done in place, override ${out.dex.input.absolute.dir} */
<target name="-post-compile"> <target name="-post-compile">
</target> </target>
--> -->
<!-- Import the actual build file.
<!-- Execute the Android Setup task that will setup some properties
specific to the target, and import the build rules files.
The rules file is imported from
<SDK>/platforms/<target_platform>/ant/ant_rules_r#.xml
To customize existing targets, there are two options: To customize existing targets, there are two options:
- Customize only one target: - Customize only one target:
- copy/paste the target into this file, *before* the - copy/paste the target into this file, *before* the
<setup> task. <import> task.
- customize it to your needs. - customize it to your needs.
- Customize the whole script. - Customize the whole content of build.xml
- copy/paste the content of the rules files (minus the top node) - copy/paste the content of the rules files (minus the top node)
into this file, *after* the <setup> task into this file, replacing the <import> task.
- disable the import of the rules by changing the setup task
below to <setup import="false" />.
- customize to your needs. - customize to your needs.
***********************
****** IMPORTANT ******
***********************
In all cases you must update the value of version-tag below to read 'custom' instead of an integer,
in order to avoid having your file be overridden by tools such as "android update project"
--> -->
<setup /> <!-- version-tag: 1 -->
<import file="${sdk.dir}/tools/ant/build.xml" />
</project> </project>