Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WIP: Allow reusing existing kernel tree as-is #6469

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

WIP: Allow reusing existing kernel tree as-is #6469

wants to merge 1 commit into from

Commits on Apr 4, 2024

  1. WIP: Allow reusing existing kernel tree as-is 

    This skips all git checkout, patching, configuring and cleaning when
USE_EXISTING_KERNEL_TREE=yes is passed.

This can be useful when doing kernel development by making changes
directly to the kernel sourcetree in `cache/sources`, while still
allowing to use the `compile.sh` to use the same compilation commands,
deb package building, ccache, etc. It is also useful when bisecting
a kernel issue.

Can be used something like this:

	USE_EXISTING_KERNEL_TREE=yes ./compile.sh default kernel

To produce a kernel deb in a few minutes ready to be installed on
a device.

This is mostly a proof of concept to explore the usecase. In particular:
 - I am not happy with the USE_EXISTING_KERNEL_TREE name yet.
 - I wonder if this variable should maybe be split into different ones
   (e.g. for skipping git checkout, patching, config, clean already
   has one that can be used).
 - Or maybe it would be better to split off some code out of
   compile_kernel() and expose a kernel_build and/or kernel_package
   command from ./compile.sh instead?
    @matthijskooijman
    matthijskooijman committed Apr 4, 2024
    Configuration menu
    Copy the full SHA
    799fb83 View commit details
    Browse the repository at this point in the history