a94cf0c781
HALs are starting to move to blueprint files, which means that pathmap ifeqs no longer work. This results in modules with the same name in different platform HAL directories. Since these modules aren't used or linked anywhere outside the HAL directories and a device's device.mk, we can safely use a soong namespace to isolate the different HAL directories' blueprints. This defines the PRODUCT_SOONG_NAMESPACES make flag so make knows which namespace to look in as well. Change-Id: I549e6da863465d79b12c7453aa169d5d963afa52
LineageOS =========== Getting started --------------- To get started with Android/LineageOS, you'll need to get familiar with [Repo](https://source.android.com/source/using-repo.html) and [Version Control with Git](https://source.android.com/source/version-control.html). To initialize your local repository using the LineageOS trees, use a command like this: ``` repo init -u git://github.com/LineageOS/android.git -b lineage-16.0 ``` Then to sync up: ``` repo sync ``` Please see the [LineageOS Wiki](https://wiki.lineageos.org/) for building instructions, by device. Submitting patches ------------------ Patches are always welcome! Please submit your patches via LineageOS Gerrit! Simply follow our guide on [how to submit patches](https://wiki.lineageos.org/submitting-patch-howto.html). To view the status of your and others' patches, visit [LineageOS Gerrit Code Review](https://review.lineageos.org/). Buildbot -------- All supported devices are built weekly and periodically as changes are committed to ensure the source trees remain buildable. You can view the current build statuses at [LineageOS Jenkins](https://jenkins.lineageos.org/). Builds produced weekly by the buildbot can be downloaded from [LineageOS downloads](https://download.lineageos.org/).