- Around 75G disk space
- 20G or more usable internet
- A computer with at least 8G RAM running Linux or MacOS
- A brain
-
Preparing the sauce
- Make sure you have a build environment setup.
- Make a new directory, cd to it and run
mkdir -p ~/hornbill repo init -u https://github.com/HornbillOS/manifest -b eleven; repo sync --force-sync; - The ROM sauce is ready! Get ready to prepare your device-specific sauce.
-
Preparing device sauce
- Define all relevant device repositories in
.repo/local_manifests/local_manifests.xml - Run
repo sync; - Move/copy your
<ROM>.mk(Example:lineage.mk) file toaosp.mk. - Open this file and
- Set PRODUCT_NAME to
aosp_<device>(Example:aosp_beryllium) - For a Phone or tablet with a SIM Card, add
# Inherit from HornbillOS vendor $(call inherit-product, vendor/aosp/config/common_full_phone.mk) - For a WiFi-only tablet, add
# Inherit from HornbillOS vendor $(call inherit-product, vendor/aosp/config/common_full_tablet_wifionly.mk)
- Set PRODUCT_NAME to
- Save and exit
- Define all relevant device repositories in
-
Cooking
- Run
Example:
source build/envsetup.sh; lunch aosp_<device>-userdebug make -j$(nproc --all) baconsource build/envsetup.sh; lunch aosp_beryllium-userdebug make -j$(nproc --all) bacon - This will start compiling the build. Now you can go for walk, play or do whatever you want until this completes.
- Resolve errors if any and continue building.
- Run
- You can reach us at Telegram
- For common porting related errors, visit Rom development
- Make sure you provide relevant logs, screenshots and details with all sources you used.
- For adding your device to the list of supported devices, please reach us at Telegram with your device tree and previous works.
