Compiling kernels with envkernel.sh: Difference between revisions
fixed the directory names and made clear where that script can be found |
|||
Line 42: | Line 42: | ||
The <code>envkernel.sh</code> script will set up a build environment based on the target device configured for <code>pmbootstrap</code>. | The <code>envkernel.sh</code> script will set up a build environment based on the target device configured for <code>pmbootstrap</code>. | ||
Make sure to replace the example names with your correct device name. When running <code>pmbootstrap init</code>, the correct target device needs to be selected. Most devices should include a link to their kernel package at the bottom of their wiki page. | |||
<syntaxhighlight lang="shell-session"> | <syntaxhighlight lang="shell-session"> | ||
Line 48: | Line 48: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Run the <code>envkernel.sh</code> script once in the kernel source directory to initialize the build environment. If the kernel can only be compiled with GCC6 then pass the <code>--gcc6</code> flag. | Run the <code>envkernel.sh</code> script (found in the pmbootstrap git repository) once in the kernel source directory to initialize the build environment. If the kernel can only be compiled with GCC6 then pass the <code>--gcc6</code> flag. | ||
<syntaxhighlight lang="shell-session"> | <syntaxhighlight lang="shell-session"> | ||
$ source | $ source pmbootstrap/helpers/envkernel.sh --gcc6 | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Copy the defconfig from the kernel aport to the kernel source directory. | Copy the defconfig from the kernel aport to the kernel source directory. Replace the defconfig file that your build would use. | ||
<syntaxhighlight lang="shell-session"> | <syntaxhighlight lang="shell-session"> | ||
$ cp / | $ cp ~/.local/var/pmbootstrap/cache_git/pmaports/device/testing/linux-wiki-example/config-linux-wiki-example.aarch64 arch/arm64/configs/example_defconfig | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Build the defconfig and kernel with the following commands. | Build the defconfig and kernel with the following commands. | ||
<syntaxhighlight lang="shell-session"> | <syntaxhighlight lang="shell-session"> | ||
$ make | $ make example_defconfig | ||
$ make | $ make | ||
</syntaxhighlight> | </syntaxhighlight> |
Revision as of 01:24, 1 October 2023
This page details how to compile a kernel manually using the envkernel.sh
helper script as well as how to package and install a locally compiled kernel. This workflow can be used to quickly iterate and test during kernel development by using the existing kernel packaging and upgrade process to install a development kernel.
Usually when compiling a kernel, you would install all dependencies and a cross compiler in your host system. To make it easier, we have the envkernel.sh
script (for fish shell: envkernel.fish
). It sets up an Alpine Linux chroot with all the dependencies by using pmbootstrap
internally, exports the environment variables to use the right cross compiler and creates an alias to make
. This means, whenever you type make
after sourcing that script, it will actually run make
in the chroot.
Selecting a kernel
This section details how to fetch the kernel source of an existing postmarketOS device. Existing kernel aports can be found in the aports/device
directory.
In the following example we will use the oneplus-bacon
device. The kernel aport is in the aports/device/linux-oneplus-bacon
directory. Within the APKBUILD is the source
variable which lists the kernel source repository.
After determining the kernel you want to work with, download the source code.
$ git clone https://github.com/LineageOS/android_kernel_oneplus_msm8974.git
$ cd android_kernel_oneplus_msm8974
Preparing the source directory
To compile the current version of the kernel, check out the git revision found in the APKBUILD.
$ git checkout dd65620ba04a8c6ba0e30553c9c95388daefae02 # example
Applying patches
Some kernel aports have patches applied on top of the remote source. You may want to apply these patches if they aren't in the source tree you have checked out.
For example oneplus-bacon
has a patch which isn't in the git revision in the prior example.
$ git apply /code/pmboostrap/aports/device/linux-oneplus-bacon/02_gpu-msm-fix-gcc5-compile.patch
Kernels which can only be compiled with older GCC versions may need the compiler-gcc6.h
. If this header exists in the kernel aport then copy it to the kernel source directory.
$ cp /code/pmboostrap/aports/device/linux-oneplus-bacon/compiler-gcc6.h include/linux/
Compile the kernel
The envkernel.sh script is not provided when you installed pmbootstrap from pip. You have to install pmbootstrap from git to have it. |
The envkernel.sh
script will set up a build environment based on the target device configured for pmbootstrap
.
Make sure to replace the example names with your correct device name. When running pmbootstrap init
, the correct target device needs to be selected. Most devices should include a link to their kernel package at the bottom of their wiki page.
$ pmbootstrap init
Run the envkernel.sh
script (found in the pmbootstrap git repository) once in the kernel source directory to initialize the build environment. If the kernel can only be compiled with GCC6 then pass the --gcc6
flag.
$ source pmbootstrap/helpers/envkernel.sh --gcc6
Copy the defconfig from the kernel aport to the kernel source directory. Replace the defconfig file that your build would use.
$ cp ~/.local/var/pmbootstrap/cache_git/pmaports/device/testing/linux-wiki-example/config-linux-wiki-example.aarch64 arch/arm64/configs/example_defconfig
Build the defconfig and kernel with the following commands.
$ make example_defconfig
$ make
Run the kernel
Post make scripts
Some kernels require extra packaging steps such as dtbtool
. The envkernel.sh
build environment works within the pmbootstrap chroots. The run-script
alias can be used to execute scripts within the source or build directory in the chroot.
In this example we are using the oneplus-bacon
which requires dtbtool
. Create a script with the dtbtool
command named post-make.sh
in the kernel source directory.
#!/bin/sh
dtbTool -s 2048 -p "${srcdir}/scripts/dtc/" -o \
"${builddir}/arch/arm/boot/dt.img" \
"${builddir}/arch/arm/boot"
Run the script.
$ run-script post-make.sh
Packaging and flashing the kernel
A kernel compiled under envkernel.sh
can be packaged by pmbootstrap by using the --envkernel
build option.
$ pmbootstrap build --envkernel linux-oneplus-bacon
Usually if the device boots to SSH with USB networking and has support for kernel upgrades, you can install the new kernel by sideloading.
$ pmbootstrap sideload linux-oneplus-bacon
After compiling and packaging the kernel, it can be flashed to device using the standard pmbootstrap flash commands. Note that if your kernel includes kernel modules (most mainline kernels do) these will not be installed and some features might break when you boot back up. In this case you can sideload as above once you have a booting kernel.
$ pmbootstrap flasher flash_kernel
Packaging kernels built without envkernel
As of !2175 the envkernel packaging logic can be used to package kernels built directly on the host. This is intended to allow folks who prefer to set up their own kernel building environment to still make use of pmbootstrap for packaging and sideloading the new kernel.
Currently this requires that you use .output
as your output directory (add O=.output
as an argument to make). With that done just build your kernel as normal and follow the packaging/flashing steps above.
See also
- !1703 optional gcc6 argument
- !1747 pmbootstrap build --envkernel
- a quick Q&A about using envkernel.sh for the Nexus 5 (if you have more questions, please open a new issue or ask in the chat).
- !2175 support for using the envkernel packaging logic on kernels built on the host