forked from servalproject/batphone
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathbuild.xml
More file actions
165 lines (135 loc) · 6.87 KB
/
build.xml
File metadata and controls
165 lines (135 loc) · 6.87 KB
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
162
163
164
165
<?xml version="1.0" encoding="UTF-8"?>
<project name="batphone" default="help">
<!-- The local.properties file is created and updated by the 'android' tool.
It contains the path to the SDK and NDK. It should *NOT* be checked into
Version Control Systems. -->
<loadproperties srcFile="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 environment="env"/>
<!-- provides all environmental variables as env.FOO -->
<condition property="sdk.dir" value="${env.SDK_ROOT}">
<isset property="env.SDK_ROOT"/>
</condition>
<condition property="ndk.dir" value="${env.NDK_ROOT}">
<isset property="env.NDK_ROOT"/>
</condition>
<!-- quick check on sdk.dir -->
<fail
message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or set an SDK_ROOT environment variable."
unless="sdk.dir"
/>
<!-- quick check on ndk.dir -->
<fail
message="Please set ndk.dir in local.properties or an NDK_ROOT environment variable"
unless="ndk.dir"
/>
<!-- version code must be set before loading main_rules.xml -->
<exec executable="sh" dir="${basedir}" outputproperty="version.code" failifexecutionfails="false">
<arg value="-c"/>
<arg value="./git rev-list HEAD | wc -l | sed 's/ //g'"/>
</exec>
<exec executable="./git" dir="${basedir}" outputproperty="version.name">
<arg value="describe" />
</exec>
<property name="version.code" value="12345"/>
<!-- extension targets. Uncomment the ones where you want to do custom work
in between standard targets -->
<target name="chipset">
<delete file="${basedir}/data/conf/chipset.zip"/>
<zip basedir="${basedir}/data/conf/wifichipsets" destfile="${basedir}/data/conf/chipset.zip" level="9"/>
</target>
<target name="version">
<echo>Version Name: ${version.name}</echo>
<echo>Version Code: ${version.code}</echo>
<echo file="${basedir}/res/values/version.xml" append="false"><?xml version="1.0" encoding="utf-8"?><resources><string name="version">${version.name}</string></resources></echo>
</target>
<target name="res-zip">
<copy file="${basedir}/libs/armeabi/adhoc" tofile="${basedir}/data/bin/adhoc" overwrite="true" failonerror="true"/>
<copy file="${basedir}/libs/armeabi/batmand" tofile="${basedir}/data/bin/batmand" overwrite="true" failonerror="true"/>
<copy file="${basedir}/libs/armeabi/dna" tofile="${basedir}/data/bin/dna" overwrite="true" failonerror="true"/>
<copy file="${basedir}/libs/armeabi/iwlist" tofile="${basedir}/data/bin/iwlist" overwrite="true" failonerror="true"/>
<copy file="${basedir}/libs/armeabi/olsrd" tofile="${basedir}/data/bin/olsrd" overwrite="true" failonerror="true"/>
<delete file="${basedir}/assets/serval.zip"/>
<zip basedir="${basedir}/data" destfile="${basedir}/assets/serval.zip" level="9"/>
<exec executable="sh" dir="${basedir}" failifexecutionfails="false">
<arg value="-c"/>
<arg value="./git ls-files -o -s data/ > assets/manifest"/>
</exec>
</target>
<target name="upload-chipset" depends="chipset">
<exec executable="scp" dir="${basedir}">
<arg value="${basedir}/data/conf/chipset.zip"/>
<arg value="${webserver}/chipset.zip"/>
</exec>
</target>
<target name="upload-release" depends="version">
<exec executable="scp" dir="${basedir}">
<arg value="${basedir}/bin/batphone-release.apk"/>
<arg value="${webserver}/files/Serval-${version.name}.apk"/>
</exec>
</target>
<target name="ndk-build">
<exec executable="${ndk.dir}/ndk-build" failonerror="true"/>
</target>
<target name="-pre-build" depends="version,ndk-build,res-zip,chipset">
</target>
<target name="clean-all" depends="clean">
<exec executable="${ndk.dir}/ndk-build" failonerror="true">
<arg value="clean"/>
</exec>
<delete file="${basedir}/data/bin/adhoc" quiet="true"/>
<delete file="${basedir}/data/bin/batmand" quiet="true"/>
<delete file="${basedir}/data/bin/dna" quiet="true"/>
<delete file="${basedir}/data/bin/iwlist" quiet="true"/>
<delete file="${basedir}/data/bin/olsrd" quiet="true"/>
</target>
<target name="-pre-compile"/>
<!--
/* 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: custom -->
<import file="${sdk.dir}/tools/ant/build.xml" />
</project>