Mahtan/wagic
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revert android build file, wasn't intended to be part of the previous commit

Browse Source
This commit is contained in:
Xawotihs
2012-01-09 23:44:29 +00:00
parent b4c33cb3e1
commit 9161136797
1 changed files with 45 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

108
projects/mtg/Android/build.xml
View File

@@ -1,85 +1,67 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<project name="Wagic" default="help"> <project name="Wagic">
<!-- 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 into It contains the path to the SDK. It should *NOT* be checked in in Version
Version Control Systems. --> Control Systems. -->
<loadproperties srcFile="local.properties" /> <property file="local.properties" />
<!-- The ant.properties file can be created by you. It is only edited by the <!-- The build.properties file can be created by you and is never touched
'android' tool to add properties to it. by the 'android' tool. This is the place to change some of the default property values
This is the place to change some Ant specific build properties. used by the Ant rules.
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'.
For other overridable properties, look at the beginning of the rules Properties related to the SDK location or the project target should be updated
files in the SDK, at tools/ant/build.xml using the 'android' tool with the 'update' action.
Properties related to the SDK location or the project target should This file is an integral part of the build system for your application and
be updated using the 'android' tool with the 'update' action. should be checked in in Version Control Systems.
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" /> <property file="build.properties" />
<!-- The project.properties file is created and updated by the 'android' <!-- The default.properties file is created and updated by the 'android' tool, as well
tool, as well as ADT. 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" />
This contains project specific properties such as project target, and library <!-- Custom Android task to deal with the project target, and import the proper rules.
dependencies. Lower level build properties are stored in ant.properties This requires ant 1.6.0 or above. -->
(or in .classpath for Eclipse projects). <path id="android.antlibs">
<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>
This file is an integral part of the build system for your <taskdef name="setup"
application and should be checked into Version Control Systems. --> classname="com.android.ant.SetupTask"
<loadproperties srcFile="project.properties" /> classpathref="android.antlibs" />
<!-- quick check on sdk.dir --> <!-- Execute the Android Setup task that will setup some properties specific to the target,
<fail and import the build rules files.
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
<!-- extension targets. Uncomment the ones where you want to do custom work To customize some build steps for your project:
in between standard targets --> - copy the content of the main node <project> from android_rules.xml
<!-- - paste it in this build.xml below the <setup /> task.
<target name="-pre-build"> - disable the import by changing the setup task below to <setup import="false" />
</target>
<target name="-pre-compile">
</target>
/* This is typically used for code obfuscation. This will ensure that the properties are setup correctly but that your customized
Compiled code location: ${out.classes.absolute.dir} build steps are used.
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 --> <setup />
<import file="${sdk.dir}/tools/ant/build.xml" />
</project> </project>