66ce59c88e
* 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
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/).