build: Add chromium prebuilt support to envsetup.sh && The core Makefile

This adds a chromium_prebuilt function to envsetup.sh that is invoked by lunch to check
whether the chromium prebuilts are up-to-date or not. If not, it will be built from source
and then the new source built version will be pulled during brunch/mka bacon to become the
new prebuilts for future builds.

This is all opt-in through the USE_PREBUILT_CHROMIUM flag. Without it being set to 1,
none of this would be ran, and regular operations will go on.

PS13:
-use export TARGET_DEVICE
-replace git -C with params compatible to old git versions

(vendor repository for script)

Change-Id: I40f8c8dbd2a8a84a5c1b9f47ee04180a71ef4e07
Prebuilt chromium: Run a check for target device directory

this should fix the issue that arises if device fails and device is built again,
chromium will error out because it thinks the prebuilt files exist (which they are
not, directories are just created).

Signed-off-by: Ayysir <ayysir@aospal.com>
Change-Id: I595cab268e66c738ccae9900150b36d7f9626a6e
Update CM's repopick python script

Signed-off-by: Andre Saddler <dresadd09691@gmail.com>
Change-Id: Ic6a3fa2950aac3596c5547c9811791bbcf2ebe33
Repopick: update legacy gerrit api

Change-Id: Ic21c2aac1c27f29e1ee052b277dd6497342889b2
Repopick: remove legacy gerrit port

Change-Id: Ib1a7be3399eaac9f24dd835dc003c4ebb7ac4856
Migrate telephony packages (2/2)

PS2:
* Add remaining telephony packages from vendor/pa/configs/telephony.mk
* Clean up

Signed-off-by: Ayysir <ayysir@aospal.com>
Change-Id: Ie15663544155f5613bc8ca1362f4d2affb3b6d7f
roomservice: handle GitHub's api changes

while other teams flood their gerrit, we just reformat our device string

GitHub support reply:
-------------------------------------
Hi Alexander Martinz,

> sorry to bother you, but our automated builds, which use the github search api
> to locate repositories, are constantly failing with some specific repositories.
>
> example url: https://api.github.com/search/repositories?q=user:NamelessRom+android_device+find7+fork:true

Sorry for the trouble!  Our search folks investigated and it looks like the issue
is how we tokenize repository names.

We're splitting "find7" into 2 separate tokens ("find" and "7"),
so searching for "find7" returns no results like you found.

This is why dropping the "7" works, or if you search for "7" separately,
it works as well:

https://api.github.com/search/repositories?q=user:NamelessRom+android_device+find+7+fork:true

Does that clear things up?
If this is a problem for your build process however, please let us know.

Thanks,
Robert

-------------------------------------

Change-Id: I111cb5dd1804d183811a2765f13d930d564d2cf5
build: qcom: Set QCOM_*_PATH variables for hardware/qcom-* projects

This consolidates a bunch of one-off logic scattered throughout the
code base.  Usage in Android.mk files is trivial:

At top level, use e.g. "ifeq ($(call my-dir),$(QCOM_AUDIO_PATH))".
This works for all variants, including non-variants (i.e. AOSP).

Within subdirs, use e.g. hardware/qcom/audio => $(QCOM_AUDIO_PATH)

Change-Id: Iee2497ea9a7efeb4ae9e861b84c532b19da7b69d
build: Introduce project pathmap and use it for qcom variants

The project pathmap tracks the path to the top level of a project.  The
following functions are provided:

 * project-set-path adds an entry.
 * project-set-path-variant adds a "variant" entry.
 * project-path-for retrieves an entry.

To use as a guard in Android.mk:

  ifeq ($(call my-dir),$(call project-path-for,projectname))

To use for include paths in Android.mk:

  LOCAL_C_INCLUDES += $(call project-path-for,projectname)/...

Set project pathmap for qcom project variants.

Change-Id: I8dceca72a1ba80fc7b1830c5ab285d444f530457
build: Set QCOM variants for non-QCOM_HARDWARE defined targets

* Nexus devices and others typically do not define the QCOM_HARDWARE
  flag, so the variant path should always default to the AOSP variant.
* Unconditionally set the variant to the AOSP HAL by default.

Change-Id: I714170897128f92718af266366cfcbf3136e8981
build: Add "dtbs" target when building the kernel

 * This is needed for 3.10

Change-Id: I4044ea9e67017452efc25097a3327141a6627c24
repopick: allow specifying a topic to pick all commits from

Change-Id: I4fb60120794a77986bf641de063a8d41f4f45a23
make rules for building on OSX 10.9 (Mavericks) and 10.10 (Yosemite B4)

Change-Id: I8dfc5c4148dec7f8badc814acfb32ea41e8f24d2
build: Use project pathmap for recovery

Change-Id: I6339ac77b899a43db21261d587252b65cb58ad79
Revert "Add the keys I used to sign the market version of Superuser."

These are obsolete.

This reverts commit 0f15d18a50d721faa8dee67f763405354025e25a.

Change-Id: I645686c5049f8651e99c95f2b775aaae2cca1f3a
releasetools: Properly handle custom values for tools

Rather than writing these values to their own files, store them
in the target_files META/misc_info.txt. This way, we don't need to
download and parse through multiple files when using signing/release
tools.

Change-Id: I6f845fc055e4ef2ed4adf9628cca505e99b2a9fa
KTU84Q
build: Disable Tamil locale

With only 3% approved in CM project and 1% on AOSP project
in the past 5 months, this is a no-go

Change-Id: I0c9d31d5737a2191e9a425b9de98ca659071ad7d
ota: Make sure we don't install on top of an incompatible system

If the system has data present, make sure said data doesn't depend
on a system signature different from our own. If we can't find
our platform key, abort the installation

Change-Id: I16572daf9464de326a9d0d126597cfbf03208f94
build: Store the jenkins build number in misc_info

If the jenkins build number is available, list it as build_number in
the misc_info.txt file.

Change-Id: I6500c6b53661f2904dff738d25d8a8d24a7dca80