...binaries and libraries

* We need it to be in the rpath during the build because we use
  aapt to build other packages here, like android-framework-res.
* However, there's no reason the installed binary should have that,
  so use patchelf to set the approrpriate rpath.

* It's still a work in progress, and can't be used /
  released right now.
* Move it to a different branch which can be merged back into master
  when it becomes usable / releasable.

Signed-off-by: Chirayu Desai <chirayudesai1@gmail.com>

* It builds the resources from core/res using aapt, and installs
  the file to /usr/lib/android-sdk/framework-res.apk
  The location was something I picked for temporary use, and an
  appropriate location can be decided before pushing this to alioth.

d/rules: No longer need export DEB_BUILD_MAINT_OPTIONS = hardening=+all: bindnow and PIE will soon be default in Stretch

"android.jar" and "uiautomator.jar" are built from API stubs without any real
functionality or Javadoc comment, which are generated using Doclava.
Following are the changes:
  * Set Java class version to 1.7 since Android 6 uses OpenJDK 7.
  * Modify debian/build.gradle to make use of Doclava.
  * Drop all build-dependencies previously used to compile "android.jar" since
    Doclava do not need them to generate the stubs.
  * Also drop the patches that fix third-party packages' namespaces.
  * Extract some JUnit files from AOSP's repo since "android.jar" contains
    these classes and Doclava can not generate stubs without a source file.
  * Drop Javadoc packages since the classes are simply stubs without any
    documentations.
  * First generate an "all-event-log-tags.txt" before compiling AIDL files.
    This is for complying with upstream's behavior.
At this point the pacakge is buildable again.

aapt_Images_cpp_remove_assertions.diff. This patch now removes some assertions
instead of patching the API usage.

For unidentified reasons, the assertions in
checkNinePatchSerialization(Res_png_9patch *,  void *) always fail, which
prevents aapt from outputting any APKs or JARS.
If they are not removed, the fact that they are using the wrong API of
Res_png_9patch would also prevent aapt from being successfully compiled.
AOSP has not changed the API but still builds aapt, which means the
assertions are disabled. Hence it is safe to remove them.

Include resources files compiled by aapt into android.jar instead of directly include the original raw files

Upstream version 6.0.1+r43

# gpg: 由 2016年05月28日 (週六) 14時51分45秒 CST 建立的簽章, 使用 RSA 金鑰 ID 37FE9825
# gpg: 完好的簽章來自於 "殷启聪 (Simplified Chinese) <seamlikok@gmail.com>"
# gpg:                 亦即 "Kai-Chung Yan (seamlik) <seamlikok@gmail.com>"
# gpg:                 亦即 "QICONG YIN (Passport English) <seamlikok@gmail.com>"
# gpg:                 亦即 "殷啟聰 (Traditional Chinese) <seamlikok@gmail.com>"
# gpg: 警告: 這把金鑰並非以受信任的簽章所認證!
# gpg:          沒有證據指出這個簽章屬於這個持有者.
#                主鑰指紋: B88A 153A DD3D 973F 3B1F  F79A DD1F AB89 37FE 9825

because dpkg-source or git-buildpackage cannot handle a symlink to a directory
in a source tarball.

  - *.zip: Not neccesary
  - packages: Contains codes required for building android.jar