This is a script which I use to compile custom kenel for my devices. It was written keeping in mind about compiling a standalone kernel in CI Deployments
Features of this script :
1. Device Specific Configuration
2. Fetching the most needed stuffs like Toolchains(clang, gcc-arm64-9.3(baremetal), gcc-arm-9.3) and Flasher(AnyKernel)(Device Specific)
3. Signs the ZipFile [AOSP Keys]
4. Builds required embedded DTBO
5. Integrate with Telegram
6. Notifies when compilation starts with some useful informations
7. Uploads build to Telegram
1. This script has most of it's stuffs in "Basic Information" part. In a nutshell,
KERENL_DIR - Points to the working directory, literally inside the actual kernel
source.
ZIPNAME - This is literally the name of our kernel which you would prefer. This
applies to the name of the zip too.
AUTHOR - It is you. Set your Name here ;)
ARCH - Architcture of your device. Most recent devices are arm64.
MODEL - Name of your device, which is known to the market.
DEVICE - The codename of your device.
DEFCONFIG - To build a kernel, you need a defconfig. It defines the defconfig which
you will need to build kernel. In case your source has the defconfig
inside /arch/arm64/configs/vendor , then you need to set it as
'/vendor/<name of your defconfig>'
COMPILER - Specifies the compiler. Make sure your kernel has all patches (if required
for your kernel).
LINKER - Specifies linker to link programs. Defaults to LLD.
INCREMENTAL- Whether you are going to clean your local source each time prior building
or not.
1 - No, You are not going to clean. Faster building times [ dirty ]
0 - Yeah, You are going to clean local everytime [ clean ]
PTTG - Abbreviation of Push To Telegram.
It is a general notifier, notifying you about build initialisation. Also
it delivers the ZIP file of the kernel.
CHATID - When you enable PTTG, you define the ID of your respective
group or channel where you want to push the build. You can use Plus
Messenger and get the ID of your group.
It is formatted as "-100<your chat ID>"
E.G. my chat ID is 1234567890, the I set it as "-1001234567890"
1 - Yes, push to telegram ( set CHATID, else everything in vain)
0 - No, thanks
DEF_REG - It generates a full defconfig from your provided defconfig and replaces
it with your main defconfig.
1 - Yes, generate a defconfig
0 - No, thanks
BUILD_DTBO - It builds a DTBO image, only flashable via AnyKernel. It is WIP and I
should suggest you to keep it off
1 - Yes, build DTBO
0 - No, thanks
SIGN - It sign the ZIP with AOSP Sign Keys for Package Signature verfication in
custom recoveries.
1 - Yes, sign the ZIP
0 - No, thanks.
SILENCE - It literally silences the compilation output. Only warnings / errors
are shown on ouput stream (terminal). It is useful to catch warnings
easily.
1 - Yes, silence the compilation
0 - No, do not do that (default)
LOG_DEBUG - Debugging purpose. Sends the compilation log on each run. Mostly needed
for monitoring(fixing warnings and errors) when cross-compiled.
1 - Yes. [self-explanatory]
0 - No. [self-explanatory]
2. You should take care of the AnyKernel repository the script is cloning. You should have
a working AnyKernel, setup for your device on a branch which is named the codename of your
device or DEVICE. Else you are pretty fucked up. I dont care if you fuck up here
3. After you finish setting up the script as per your requirements, run this in your local
bash kernel.sh
Or, if u forked it and already completed setup as per your requirement, u can simply
curl https://raw.githubusercontent.com/<YOUR_GITHUB_USERNAME>/myscripts/master/kernel.sh | bash