labyrinth

diff android/build.xml @ 5:c8826e5ebec1

- changed every data loading function to return dummy objects instead of failing - fixed mistake in AndroidManifest.xml
author John Tsiombikas <nuclear@member.fsf.org>
date Fri, 01 May 2015 05:58:41 +0300
parents
children
line diff
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/android/build.xml	Fri May 01 05:58:41 2015 +0300
     1.3 @@ -0,0 +1,92 @@
     1.4 +<?xml version="1.0" encoding="UTF-8"?>
     1.5 +<project name="labyrinth" default="help">
     1.6 +
     1.7 +    <!-- The local.properties file is created and updated by the 'android' tool.
     1.8 +         It contains the path to the SDK. It should *NOT* be checked into
     1.9 +         Version Control Systems. -->
    1.10 +    <property file="local.properties" />
    1.11 +
    1.12 +    <!-- The ant.properties file can be created by you. It is only edited by the
    1.13 +         'android' tool to add properties to it.
    1.14 +         This is the place to change some Ant specific build properties.
    1.15 +         Here are some properties you may want to change/update:
    1.16 +
    1.17 +         source.dir
    1.18 +             The name of the source directory. Default is 'src'.
    1.19 +         out.dir
    1.20 +             The name of the output directory. Default is 'bin'.
    1.21 +
    1.22 +         For other overridable properties, look at the beginning of the rules
    1.23 +         files in the SDK, at tools/ant/build.xml
    1.24 +
    1.25 +         Properties related to the SDK location or the project target should
    1.26 +         be updated using the 'android' tool with the 'update' action.
    1.27 +
    1.28 +         This file is an integral part of the build system for your
    1.29 +         application and should be checked into Version Control Systems.
    1.30 +
    1.31 +         -->
    1.32 +    <property file="ant.properties" />
    1.33 +
    1.34 +    <!-- if sdk.dir was not set from one of the property file, then
    1.35 +         get it from the ANDROID_HOME env var.
    1.36 +         This must be done before we load project.properties since
    1.37 +         the proguard config can use sdk.dir -->
    1.38 +    <property environment="env" />
    1.39 +    <condition property="sdk.dir" value="${env.ANDROID_HOME}">
    1.40 +        <isset property="env.ANDROID_HOME" />
    1.41 +    </condition>
    1.42 +
    1.43 +    <!-- The project.properties file is created and updated by the 'android'
    1.44 +         tool, as well as ADT.
    1.45 +
    1.46 +         This contains project specific properties such as project target, and library
    1.47 +         dependencies. Lower level build properties are stored in ant.properties
    1.48 +         (or in .classpath for Eclipse projects).
    1.49 +
    1.50 +         This file is an integral part of the build system for your
    1.51 +         application and should be checked into Version Control Systems. -->
    1.52 +    <loadproperties srcFile="project.properties" />
    1.53 +
    1.54 +    <!-- quick check on sdk.dir -->
    1.55 +    <fail
    1.56 +            message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable."
    1.57 +            unless="sdk.dir"
    1.58 +    />
    1.59 +
    1.60 +    <!--
    1.61 +        Import per project custom build rules if present at the root of the project.
    1.62 +        This is the place to put custom intermediary targets such as:
    1.63 +            -pre-build
    1.64 +            -pre-compile
    1.65 +            -post-compile (This is typically used for code obfuscation.
    1.66 +                           Compiled code location: ${out.classes.absolute.dir}
    1.67 +                           If this is not done in place, override ${out.dex.input.absolute.dir})
    1.68 +            -post-package
    1.69 +            -post-build
    1.70 +            -pre-clean
    1.71 +    -->
    1.72 +    <import file="custom_rules.xml" optional="true" />
    1.73 +
    1.74 +    <!-- Import the actual build file.
    1.75 +
    1.76 +         To customize existing targets, there are two options:
    1.77 +         - Customize only one target:
    1.78 +             - copy/paste the target into this file, *before* the
    1.79 +               <import> task.
    1.80 +             - customize it to your needs.
    1.81 +         - Customize the whole content of build.xml
    1.82 +             - copy/paste the content of the rules files (minus the top node)
    1.83 +               into this file, replacing the <import> task.
    1.84 +             - customize to your needs.
    1.85 +
    1.86 +         ***********************
    1.87 +         ****** IMPORTANT ******
    1.88 +         ***********************
    1.89 +         In all cases you must update the value of version-tag below to read 'custom' instead of an integer,
    1.90 +         in order to avoid having your file be overridden by tools such as "android update project"
    1.91 +    -->
    1.92 +    <!-- version-tag: 1 -->
    1.93 +    <import file="${sdk.dir}/tools/ant/build.xml" />
    1.94 +
    1.95 +</project>