-
Notifications
You must be signed in to change notification settings - Fork 110
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Anushek Prasal <anushekprasal@gmail.com>
- Loading branch information
Showing
4 changed files
with
172 additions
and
54 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,36 +1,70 @@ | ||
LineageOS | ||
Havoc-OS | ||
=========== | ||
|
||
Getting started | ||
|
||
Getting Started | ||
--------------- | ||
To get started with the Havoc-OS sources, you'll need to get | ||
familiar with [Git and Repo](https://source.android.com/setup/develop). | ||
|
||
To get started with Android/LineageOS, you'll need to get familiar with [Source Control Tools](https://source.android.com/setup/develop). | ||
|
||
To initialize your local repository using the LineageOS trees, use a command like this: | ||
``` | ||
repo init -u https://github.com/LineageOS/android.git -b lineage-20.0 --git-lfs | ||
Create the Directories | ||
---------------------- | ||
|
||
You will need to set up some directories in your build environment. | ||
|
||
To create them run: | ||
|
||
```bash | ||
mkdir -p ~/bin | ||
mkdir -p ~/havoc | ||
``` | ||
Then to sync up: | ||
|
||
Install the Repository | ||
---------------------- | ||
|
||
Enter the following to download the "repo" binary and make it executable: | ||
|
||
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo | ||
|
||
You may need to reboot for these changes to take effect. | ||
Now enter the following to initialize the repository: | ||
|
||
```bash | ||
cd ~/havoc | ||
``` | ||
repo sync | ||
|
||
|
||
To initialize your local repository, use this command: | ||
------------------------------------------------------ | ||
|
||
```bash | ||
repo init -u https://github.com/Havoc-OS/android_manifest.git -b thirteen --git-lfs | ||
``` | ||
Please see the [LineageOS Wiki](https://wiki.lineageos.org/) for building instructions, by device. | ||
|
||
To Sync the source: | ||
---------------- | ||
|
||
```bash | ||
repo sync -c -j$(nproc --all) --force-sync --no-clone-bundle --no-tags | ||
``` | ||
|
||
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). | ||
Building the System | ||
--------------- | ||
|
||
To view the status of your and others' patches, visit [LineageOS Gerrit Code Review](https://review.lineageos.org/). | ||
Please note that if you are building on Mac OS X, you are required to install coreutils from MacPorts before you continue. | ||
Initialize the environment with the envsetup.sh script. Note that replacing "source" with a single dot saves a few characters, and the short form is more commonly used in documentation. | ||
|
||
```bash | ||
. build/envsetup.sh | ||
brunch | ||
``` | ||
|
||
Buildbot | ||
-------- | ||
Enter the number of the build you want to start and press enter | ||
|
||
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 Buildkite](https://buildkite.com/lineageos). | ||
Applying for Maintainership | ||
--------------- | ||
|
||
Builds produced weekly by the buildbot can be downloaded from [LineageOS downloads](https://download.lineageos.org/). | ||
If you have successfully built for your device and want to apply for maintainership then drop in a message to SKULSHADY on Telegrams. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.