493ad4b8a5
The GCC toolchains are no longer added to the path by default, so we need to hardcode the full paths for these. Also set variables for every arch, and then set the toolchain to the arch specific var. This is so we can set the ARM32 cross compile flag for vDSO32 enabled kernels. Change-Id: I7e099a26a17f4a3cc9be6232a26c671e8fcfbdef
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-17.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/).