* Removed long ago.

Change-Id: Ic0becb9b0e2120ff8032fb046d6b0f211b82813f

dictionary is built from 4y old dictionaries which are in LatinIME
https://github.com/LineageOS/android_packages_inputmethods_LatinIME/blob/lineage-16.0/dictionaries/pl_wordlist.combined.gz
https://github.com/LineageOS/android_packages_inputmethods_LatinIME/blob/lineage-15.1/dictionaries/pl_wordlist.combined.gz
using dicttool,
dicttool build was possible thanks to
https://android.googlesource.com/platform/packages/inputmethods/LatinIME/+/a92d0f926269264e578c9162c5df230cafb99b7c

Change-Id: I4bffbb10e06c904ad58877ff920e581caa958d67

* For addonsu.

Change-Id: Ic4c701cdfe1126870258182df631192e06527fe5

* cough * someone forgot to update permissions whitelist again.

Change-Id: Iedcdb0568ea1b9924144841a8d20ca6f05bbe29b

* Note: msmnile is treated like msmnile because unlike other Qualcomm
  codenames msmnile does not expand to 8150.

Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c

* This fixes dirty boot image rebuilding on devices
  with CONFIG_LOCALVERSION_AUTO=y and any driver
  set to =m.
* Basically appending `cat include/config/kernel.release`
  to modules path makes sure that our find does not
  return old modules which would make cp fail with
  'cp: will not overwrite just-created' message.

Change-Id: Ifb79d33b95d7671d8b2d6633644c8b8290d1f442

Co-authored-by: Erfan Abdi <erfangplus@gmail.com>
Change-Id: I4881658d303b6c5c7f0b141beb50c1e9100af611

* These are pretty useful for debugging config.fs
  changes without rebuilding full system/vendor image.

Change-Id: I68fdeb2dc7c9f225784b55425407657645e34ac8

If the build is invoked off-tree, like:

    . build/envsetup.sh
    export OUT_DIR=/some/other/dir/out
    export DIST_DIR=/some/other/dir/dist
    breakfast chagalllte
    mka \
        target-files-package dist

the bootanimation.zip is correctly generated in $OUT_DIR.

However, if the user overrides directories after breakfast, i.e:

    . build/envsetup.sh
    breakfast chagalllte
    mka \
        OUT_DIR=/some/other/dir/out \
        DIST_DIR=/some/other/dir/dist \
        target-files-package dist

the destination path of intermediate bootanimation.zip is still
controlled by $ANDROID_PRODUCT_OUT which is set by build/envsetup.sh.
This leads to a copy error and a failed build.

The fix overrides $ANDROID_PRODUCT_OUT by the always-known PRODUCT_OUT
(make variable defined in build/core/envsetup.mk), making it error-prone
to environment variable declaration.

Also, the "sh" invocation is replaced with generic make-variable
$(shell).

Change-Id: Ic94d1b538fc01946b628f9b5d776548a03acde97
Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Change-Id: I8ec7771565d51f63d4ab532911454ff6865ad861

Change-Id: I249fc2abaace45324d7841e6a4ea3aeaf9e3dbe3

Change-Id: I958a6bfd1087f5437f4074e614198bb622d476ce
Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>

* Some TWRP releases expect -t parameter.

Change-Id: I5f4a55883b94e821bfcef06df7d121db1d6145a4

Fix https://gitlab.e.foundation/e/os/android_vendor_lineage/issues/15

Change-Id: I6f37adc955856fa78e719eb30249800abe80020c

* The macros used in the file formerly called "qcom_utils.mk" are
  actually generic and not QCOM-specific. Move the QCOM_BOARD definitions
  to a QCOM-specific location, and name the remaning macros something more
  generic.

Change-Id: I6747bc9201e56b456caf251122057d7dbc233f1c

* There's actually not a whole lot QC-specific about these macros,
  make them available at definition.mk inclusion time rather than
  relying on BoardConfig to include them.
* Don't create a dependency on QCOM macros from a makefile
  that is included very early in the build process.

Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67

* Regenerated using development/tools/privapp_permissions/privapp_permissions.py

Change-Id: I9f49e92dbf92dc545dee782124d45db1e70df471

* http_prebuilt.mk appears to be long gone.

Change-Id: I8ca584fc1e468bb47164984bb363f0cf29750e68

* Instead of nesting ifeq/else/ifeq/else/endif/endif construction, make
  allows the more readable ifeq/else ifeq/else/endif construction. Use it
  instead.

Change-Id: Ifd2635929799db593e04a13827f05c97e95487e4

* These shouldn't be executable.

Change-Id: Idcb4e46f0ac69116b4837cd31f9f2e506b41a3f2

* Sort the file while we are at it.

Change-Id: I8dec9ece1c1523dcb77421b6912bbef91efb1485

Change-Id: I245138b19448a193f8cbd12d5d26db295a4f4cdd

Change-Id: I5f70280e72613a8f850cb3263c45e95e80cb8b3c
Signed-off-by: Erfan Abdi <erfangplus@gmail.com>

These configuration options are set based on the Google configurations
located in kernels
(ex. https://github.com/LineageOS/android_kernel_google_wahoo/blob/lineage-16.0/build.config)

This is composed of 2 parts:

Revert "kernel: Correct CROSS_COMPILE_ARM32 toolchain"

This reverts commit c77bb3a5.
This breaks builds when building with upstream commit
ad15006cc78459d059af56729c4d9bed7c7fd860. That commit fixes LD being
used from outside the path, however androidkernel toolchains don't
have elfedit. Google specifically doesn't use androidkernel, so we
need to follow them on this.

Set CROSS_COMPILE_PREFIX to aarch64-linux-android- for clang builds

Upstream commit ad15006cc78459d059af56729c4d9bed7c7fd860 makes the
kernel build system use GCC toolchains for elfedit, so we have to
actually use a real GCC toolchain, not the androidkernel one.

Change-Id: I79ac4ac47d3ba6c2abbc5ce40e56ed5c707295b4