Android Kernel Build Action

Powered By GitHub Actions

A workflow to automatically build an Android kernel

Security Policy

See Security.md for more details.

How to use?

• First, you need to determine the kernel source code and configuration files.
• Find your kernel source repository and configure the workflow file according to the following example and README.md:

name: CI

on:
  workflow_dispatch:

permissions:
  contents: write

jobs:
  build-kernel:
    name: Build Kernel
    runs-on: ubuntu-22.04
    steps:
      - name: Build
        uses: dabao1955/kernel_build_action@main
        with:
          kernel-url: https://github.com/AcmeUI-Devices/android_kernel_xiaomi_cas
          kernel-branch: taffy
          config: cas_defconfig
          arch: arm64
          aosp-gcc: true
          aosp-clang: true
          android-version: 12
          aosp-clang-version: r383902
          anykernel3: true
          release: true
          access-token: ${{ secrets.GITHUB_TOKEN }}

Using Local Kernel Source

You can also use a local or relative path for the kernel source instead of cloning from a remote URL. This is useful when the kernel source is already checked out in the workflow.

name: CI

on:
  workflow_dispatch:

permissions:
  contents: write

jobs:
  build-kernel:
    name: Build Kernel
    runs-on: ubuntu-22.04
    steps:
      - name: Checkout kernel source
        uses: actions/checkout@v4
        with:
          repository: username/kernel_repo
          ref: main
          path: kernel/source

      - name: Build
        uses: dabao1955/kernel_build_action@main
        with:
          kernel-url: ./kernel/source/
          config: defconfig
          arch: arm64
          aosp-clang: true
          anykernel3: true

[!NOTE] - Local paths must end with / (except . for current directory) - Supported formats: ., ./, ./kernel/, ../kernel/, kernel/source/ - The directory must be a valid kernel source containing: Makefile (with VERSION), Kconfig, and arch/ directory - When using local path, kernel-branch, depth, and kernel-dir options are ignored

Or use the preset workflow file to modify it.

[!NOTE] You do not need to fork this repository.

If you just want to compile the kernel, please do not submit PR after modification!

• Finally, run the workflow you just wrote.

Inputs

FAQ

[!CAUTION] Please Read this first if you have some questions!

How to use 3rd clang？

You should disable aosp-clang and android-ndk options to use it.

Why KernelSU version built with this action is still v0.9.5？

See KernelSU 's release note for more details.

How to submit issue about features requests?

In principle, it only accepts Bug Reports and does not accept external Feature Requests; if you want new features, you are welcome to submit a Pull Request. We will still develop new features that we think are useful.

Why the workflow exits with a code with an error value of some number？

• If you get an error while downloading the toolchain or pulling the source code, please check whether your option or source code address is legitimate.
• If you encounter problems during compilation, consider replacing the source code or replacing the compiler.
• If the action has a typo problem, PR welcome!

Build failed while using third-party GCC ?

Try add LLVM=1 option with clang.

Credits

• KernelSU
• KernelSU_Action
• slimhub_actions