dan
/
tor-android
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fixing build.xml for CI server

This commit is contained in:
Nathan Freitas 2012-01-09 00:35:41 -05:00
parent 1bdbf57ffa
commit 45eb3b2afd
1 changed files with 63 additions and 45 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

108
build.xml
View File

@ -1,67 +1,85 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<project name="Orbot"> <project name="Orbot" default="help">
<!-- The local.properties file is created and updated by the 'android' tool. <!-- The local.properties file is created and updated by the 'android' tool.
It contains the path to the SDK. It should *NOT* be checked in in Version It contains the path to the SDK. It should *NOT* be checked into
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 default property values 'android' tool to add properties to it.
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:
application.package
the name of your application package as defined in the manifest. Used by the
'uninstall' rule.
source.dir source.dir
the name of the source directory. Default is 'src'. The name of the source directory. Default is 'src'.
out.dir out.dir
the name of the output directory. Default is 'bin'. The name of the output directory. Default is 'bin'.
Properties related to the SDK location or the project target should be updated For other overridable properties, look at the beginning of the rules
using the 'android' tool with the 'update' action. files in the SDK, at tools/ant/build.xml
This file is an integral part of the build system for your application and Properties related to the SDK location or the project target should
should be checked in in Version Control Systems. be updated using the 'android' tool with the 'update' action.
This file is an integral part of the build system for your
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' tool, as well <!-- The project.properties file is created and updated by the 'android'
as ADT. tool, as well as ADT.
This file is an integral part of the build system for your application and
should be checked in in Version Control Systems. -->
<property file="default.properties" />
<!-- Custom Android task to deal with the project target, and import the proper rules. This contains project specific properties such as project target, and library
This requires ant 1.6.0 or above. --> dependencies. Lower level build properties are stored in ant.properties
<path id="android.antlibs"> (or in .classpath for Eclipse projects).
<pathelement path="${sdk.dir}/tools/lib/anttasks.jar" />
<pathelement path="${sdk.dir}/tools/lib/sdklib.jar" />
<pathelement path="${sdk.dir}/tools/lib/androidprefs.jar" />
<pathelement path="${sdk.dir}/tools/lib/apkbuilder.jar" />
<pathelement path="${sdk.dir}/tools/lib/jarutils.jar" />
</path>
<taskdef name="setup" This file is an integral part of the build system for your
classname="com.android.ant.SetupTask" application and should be checked into Version Control Systems. -->
classpathref="android.antlibs" /> <loadproperties srcFile="project.properties" />
<!-- Execute the Android Setup task that will setup some properties specific to the target, <!-- quick check on sdk.dir -->
and import the build rules files. <fail
message="sdk.dir is missing. Make sure to generate local.properties using 'android update project'"
unless="sdk.dir"
/>
The rules file is imported from
<SDK>/platforms/<target_platform>/templates/android_rules.xml
To customize some build steps for your project: <!-- extension targets. Uncomment the ones where you want to do custom work
- copy the content of the main node <project> from android_rules.xml in between standard targets -->
- paste it in this build.xml below the <setup /> task. <!--
- disable the import by changing the setup task below to <setup import="false" /> <target name="-pre-build">
</target>
<target name="-pre-compile">
</target>
This will ensure that the properties are setup correctly but that your customized /* This is typically used for code obfuscation.
build steps are used. Compiled code location: ${out.classes.absolute.dir}
If this is not done in place, override ${out.dex.input.absolute.dir} */
<target name="-post-compile">
</target>
-->
<!-- Import the actual build file.
To customize existing targets, there are two options:
- Customize only one target:
- copy/paste the target into this file, *before* the
<import> task.
- customize it to your needs.
- Customize the whole content of build.xml
- copy/paste the content of the rules files (minus the top node)
into this file, replacing the <import> task.
- 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>