Add logline signalling which project each section is for
Allow for Mms placement in system/priv-app and error catch for empty API

This also allows passing API as a parameter for makePatches, pretty unlikely
that will be needed elsewhere. But still, it helps.
Allow for variable baksmali location; test for presence of both jar states

KitKat is going to require baksmali-2.0.jar. This script currently allows for
both jars to be in the system. I think the best thing to do would be to bundle
the jars with the scripts.
Fix output folder on makePatches so as not to create any new folders.
Use regular 1.4 baksmali for Kitkat (for now)

The patches are failing to apply...I had heard of this before, but I thought
it was because the patches were made with 1.4. I made the patches with 2.0 and
used 2.0 in the auto-patcher---no dice. The 1.4 baksmali in the auto-patcher
had the same problem...every smali binary is producing output that rejects
patches from 2.0....hmmmmm.
Update for Android 4.4 (now the default)

This has provisions for the new AOSP placement of Mms (/system/priv-app) and
we now are using baksmali-2.0 for 4.4. As of right now, you need to get that
decompiler jar yourself.

This also adds a new user variable BAKSMALI_LOC, which is the location of the
decompiler.

Finally, the file structure and dir names of the holding folders has been
resolved. We are back to using the more sensible 'stock-framework' structure
that we have been using since jump.
Change rm -rf to rm

better discipline and more secure.