Browse Source

- Just trying to setup an ant script

langerhans 8 years ago
3 changed files with 94 additions and 0 deletions
  1. +1
  2. +1
  3. +92

+ 1
- 0
.gitignore View File

@ -0,0 +1 @@

+ 1
- 0
OneToolbox/TODO.txt View File

@ -13,6 +13,7 @@
- Higher grid size in sense launcher (Already looked into this. needs many dimens.xml changes)
- Smaller size horizontal EQS. (Could probably remove Text and reduce icon size. Not really sure if many would use it...)
- Limit number of loaded SMS in stock SMS app. One user said he has 10k SMS and it makes his phone slow... wtf?
- Gestures (to lock phone) in sense launcher. Idea I got by PM. I said not gonna happen soon :D

+ 92
- 0
OneToolbox/build.xml View File

@ -0,0 +1,92 @@
<?xml version="1.0" encoding="UTF-8"?>
<project name="Sense 5 Toolbox" default="help">
<!-- The 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="" />
<!-- The 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:
The name of the source directory. Default is 'src'.
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="" />
<!-- if sdk.dir was not set from one of the property file, then
get it from the ANDROID_HOME env var.
This must be done before we load since
the proguard config can use sdk.dir -->
<property environment="env" />
<condition property="sdk.dir" value="${env.ANDROID_HOME}">
<isset property="env.ANDROID_HOME" />
<!-- The 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
(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="" />
<!-- quick check on sdk.dir -->
message="sdk.dir is missing. Make sure to generate using 'android update project' or to inject it through the ANDROID_HOME environment variable."
Import per project custom build rules if present at the root of the project.
This is the place to put custom intermediary targets such as:
-post-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})
<import file="custom_rules.xml" optional="true" />
<!-- 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" />