wiki:BuildingBbTracker

Building bbTracker

This page will give an overview over the steps necessary to check out, build and work on bbTracker. This will be done in two parts. One presents a simple command line setup, while the other one will present a more complex and featureful setup using Eclipse.

Commandline Setup

The command line setup is enough to checkout and build bbTracker. It's presented here to make a clear distinction between necessary components and optional components. Anyone who doesn't like the tools chosen for the complete setup (such as Eclipse) can build on this and use the tools of their choice.

The minimum set of software necessary for building bbTracker from SVN contains:

Checking out the code

  • Create a directory where you want to keep your bbTracker related work.
  • Open a shell window and change to that directory
  • check out bbtracker and bbtracker_common using the following commands (bbtracker_tests contains some JUnit tests that are not yet part of the build system):
    svn co http://svn.bbtracker.org/bbtracker/trunk bbtracker
    svn co http://svn.bbtracker.org/bbtracker_common/trunk bbtracker_common
    

Configuring your environment

  • inside the bbtracker directory, create a text file called build.properties and define a property called wtk.home pointing to the directory where you installed the WTK
wtk.home=/path/to/WTK

Running Ant

When Apache Ant is setup correctly, then all that needs to be done to build bbTracker now is tun run ant from inside the bbtracker directory.

This should produce a directory called build, that contains (among others) a bbtracker.jar and a bbtracker.jad. Those two files together make up bbTracker, ready to install.

If you've not installed Proguard (see below), you'll get an error about a missing obsfuscator, but these two files will still be built.

Final Step

That's it. Now you only need to get your freshly build version of bbTracker onto your phone. How this works depends heavily on which phone you use. Some phones only support over-the-air downloads, others support installing applications from memory cards.

Adding obfuscation

It is a good idea to use  obfuscate the built jar file, in order to reduce the size, which saves both download bandwidth and device memory. To do this, download and unpack a copy of the latest version of  ProGuard.

Then modify your build.properties to add the path to proguard by setting the property wtk.proguard.home to point to your ProGuard directory:

wtk.proguard.home=/path/to/proguard

Complete Setup

The complete setup involves the following software:

Detailed instructions on how to install all that will be added, as necessary.