forked from dimagi/commcare-android
-
Notifications
You must be signed in to change notification settings - Fork 0
/
build.xml
161 lines (129 loc) · 5.96 KB
/
build.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
<?xml version="1.0" encoding="UTF-8"?>
<project name="commcare-odk" default="help">
<!-- The local.properties file is created and updated by the 'android' tool.
It contains the path to the SDK. It should *NOT* be checked into
Version Control Systems. -->
<property file="local.properties" />
<!-- The ant.properties file can be created by you. It is only edited by the
'android' tool to add properties to it.
This is the place to change some Ant specific build properties.
Here are some properties you may want to change/update:
source.dir
The name of the source directory. Default is 'src'.
out.dir
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
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="ant.properties" />
<!-- The project.properties file is created and updated by the 'android'
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
application and should be checked into Version Control Systems. -->
<loadproperties srcFile="project.properties" />
<property file="${file.key.properties}" />
<property file="${file.remote.properties}" />
<!-- quick check on sdk.dir -->
<fail
message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through an env var"
unless="sdk.dir"
/>
<target name="-pre-build">
<!-- we actually need to wipe out all of our libs now, since they're in ODK's library -->
<delete dir="${jar.libs.dir}"/>
<mkdir dir="${jar.libs.dir}"/>
</target>
<target name="cc-setup" depends="build-from-source, addversionnumber">
<mkdir dir="${jar.libs.dir}"/>
<!-- copy libraries -->
<copy todir="${jar.libs.dir}">
<fileset dir="lib"/>
</copy>
<!-- update resources -->
<tstamp>
<format property="TODAY_TIMESTAMP"
pattern="MMMM-dd-yyyy"/>
</tstamp>
<mkdir dir="${custom.dir.resource}"/>
<copy todir="${custom.dir.resource}">
<fileset dir="res"/>
</copy>
<replace file="${custom.dir.resource}/values/external_strings.xml" token="UNKNOWN_DATE" value="${TODAY_TIMESTAMP}"/>
<replace file="${custom.dir.resource}/values/external_strings.xml" token="CUSTOM_BUILD" value="${version.code}"/>
<replace file="${custom.dir.resource}/values/external_strings.xml" token="MAPS_KEY" value="${maps.api.key}"/>
</target>
<target name="odk-setup">
<mkdir dir="${odk.libs}"/>
<!-- Copy over original odk libs -->
<copy todir="${odk.libs}" overwrite="true">
<fileset dir="${odk.libs.orig}" includes="*.jar"/>
</copy>
<!-- copy CCODK versions (to ensure compatibility) -->
<copy todir="${odk.libs}" overwrite="true">
<fileset dir="libs"/>
</copy>
</target>
<target name="build-from-source" if="build.source">
<mkdir dir="${jar.libs.dir}"/>
<!-- todo: that -->
<copy todir="${jar.libs.dir}">
<fileset dir="${javarosa.libs}" includes="*.jar"/>
<fileset dir="${commcare.libs}" includes="*.jar"/>
</copy>
</target>
<target name="addversionnumber" if="build.server">
<property name="android.version.code" value="android:versionCode="/>
<replaceregexp file="AndroidManifest.xml"
match='android:versionCode="(.*)"'
replace='${android.version.code}"${version.code}"'/>
</target>
<!-- extension targets. Uncomment the ones where you want to do custom work
in between standard targets -->
<!--
<target name="-pre-build">
</target>
<target name="-pre-compile">
</target>
/* This is typically used for code obfuscation.
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"
-->
<!-- version-tag: 1 -->
<import file="${sdk.dir}/tools/ant/build.xml" />
<target name="prepare" depends="cc-setup, odk-setup"/>
<target name="cc-release" depends="prepare, release">
</target>
<target name="run-tests" if="build.run.tests">
<ant antfile="${dir.test.project}/build.xml" target="all" inheritAll="false" inheritRefs="false">
<!--property name="compile.source" value="${compile.source}"/-->
<property name="avd.name" value="${avd.name}"/>
<property name="sdk.home" value="${sdk.home}"/>
</ant>
</target>
<target name="test-and-release" depends="prepare, run-tests, cc-release"/>
</project>