Hello all,

 

maybe I missed that part in the docs or in another thread... In fact, I haven't found a solution.

 

I'd like to include a custom kernel repository in the build process (maybe in kernel-only mode) and select that in the interface if available. Either include a remote directory (github...) or some local directory. That all for easily trying things out without using the single-patches directory but using the armbian building environment.

I couldn't find the lines in the build scripts, where I easily can "hardcode" such a kernel tree.

Ultimate way would be an additional option for a custom kernel tree, chooseable via the menu.

 

Can someone point me into the right direction?

 

Thanks

rellla

Our documentation does not follow the speed of our development

 

Use userpatches/lib.config override as following example:

BOOTBRANCH="branch:2015.10.fslc-qdl"
BOOTSOURCE="https://github.com/UDOOboard/uboot-imx"
BOOTDIR="xxdir"
KERNELSOURCE="https://github.com/UDOOboard/linux_kernel"
KERNELBRANCH="branch:3.14-1.0.x-udoo-ov772x"
KERNELDIR="yydir"

This will be forced for all boards ...

Use userpatches/lib.config override [...] This will be forced for all boards ...

 

That's why this commit implemented a 'per $LINUXFAMILY' override, eg. userpatches/sources/sun7i.conf

Thanks guys, this was exactly what i need.

rellla

One additional thing though:

 

Maybe https://github.com/igorpecovnik/lib/blob/master/configuration.sh#L76should be moved to line 106 or 186 in order to be able to also set $LINUXCONFIG ?!

 

rellla

@rellla

You can put your customized kernel config in userpatches too: https://github.com/igorpecovnik/lib/blob/master/common.sh#L214-L216

Oh. Very customizable

Thanks!

 

rellla