Search
lxdream.org :: lxdream/android/build.xml :: diff
lxdream 0.9.1
released Jun 29
Download Now
filename android/build.xml
changeset 1239:be3121267597
next1245:01e0020adf88
author nkeynes
date Sat Feb 25 21:30:49 2012 +1000 (8 years ago)
permissions -rw-r--r--
last change Android support WIP
file annotate diff log raw
1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/android/build.xml Sat Feb 25 21:30:49 2012 +1000
1.3 @@ -0,0 +1,79 @@
1.4 +<?xml version="1.0" encoding="UTF-8"?>
1.5 +<project name="Lxdream" default="help">
1.6 +
1.7 +<!-- The local.properties file is created and updated by the 'android'
1.8 + tool.
1.9 + It contains the path to the SDK. It should *NOT* be checked into
1.10 + Version Control Systems. -->
1.11 + <property file="local.properties" />
1.12 +
1.13 + <!-- The build.properties file can be created by you and is never touched
1.14 + by the 'android' tool. This is the place to change some of the
1.15 + default property values used by the Ant rules.
1.16 + Here are some properties you may want to change/update:
1.17 +
1.18 + source.dir
1.19 + The name of the source directory. Default is 'src'.
1.20 + out.dir
1.21 + The name of the output directory. Default is 'bin'.
1.22 +
1.23 + Properties related to the SDK location or the project target should
1.24 + be updated using the 'android' tool with the 'update' action.
1.25 +
1.26 + This file is an integral part of the build system for your
1.27 + application and should be checked into Version Control Systems.
1.28 +
1.29 + -->
1.30 + <property file="build.properties" />
1.31 +
1.32 + <!-- The default.properties file is created and updated by the 'android'
1.33 + tool, as well as ADT.
1.34 + This file is an integral part of the build system for your
1.35 + application and should be checked into Version Control Systems. -->
1.36 + <property file="default.properties" />
1.37 +
1.38 +
1.39 + <!-- Required pre-setup import -->
1.40 + <import file="${sdk.dir}/tools/ant/pre_setup.xml" />
1.41 +
1.42 +
1.43 +<!-- extension targets. Uncomment the ones where you want to do custom work
1.44 + in between standard targets -->
1.45 +<!--
1.46 + <target name="-pre-build">
1.47 + </target>
1.48 + <target name="-pre-compile">
1.49 + </target>
1.50 +
1.51 + [This is typically used for code obfuscation.
1.52 + Compiled code location: ${out.classes.absolute.dir}
1.53 + If this is not done in place, override ${out.dex.input.absolute.dir}]
1.54 + <target name="-post-compile">
1.55 + </target>
1.56 +-->
1.57 +
1.58 + <!-- Execute the Android Setup task that will setup some properties
1.59 + specific to the target, and import the build rules files.
1.60 +
1.61 + The rules file is imported from
1.62 + <SDK>/tools/ant/
1.63 + Depending on the project type it can be either:
1.64 + - main_rules.xml
1.65 + - lib_rules.xml
1.66 + - test_rules.xml
1.67 +
1.68 + To customize existing targets, there are two options:
1.69 + - Customize only one target:
1.70 + - copy/paste the target into this file, *before* the
1.71 + <setup> task.
1.72 + - customize it to your needs.
1.73 + - Customize the whole script.
1.74 + - copy/paste the content of the rules files (minus the top node)
1.75 + into this file, *after* the <setup> task
1.76 + - disable the import of the rules by changing the setup task
1.77 + below to <setup import="false" />.
1.78 + - customize to your needs.
1.79 + -->
1.80 + <setup />
1.81 +
1.82 +</project>
.