Related to this question. In order to customize the kernel configuration I created in my custom layer this structure:
$ tree recipes-kernel/
recipes-kernel/
└── linux
├── files
│ └── <image>-defconfig
└── linux-stm32mp_4.19.bbappend
Where the defconfig
file is actually the .config
used to manually compile the kernel (see the other question). The bbappend
file contains the following code:
SRC_URI += "file://<full-path>/meta-custom-layer/recipes-kernel/linux/files/<image>-defconfig"
KERNEL_DEFCONFIG_stm32mp1_<variant> = "{WORKDIR}/<image>-defconfig"
I'm sure the file is processed because if I change the name of the defconfig bitbake
raises a file not found error.
The problem is the compiled kernel does not have my customization.
But if I copy my defconfig to the build directory (i.e. tmp/work/stm32mp1_<variant>-openstlinux_eglfs-linux-gnueabi/linux-stm32mp/4.19-r0/linux-stm32mp1-<variant>-standard-build/.config
) and manually bitbake virtual/kernel
) it does.
So it seems it searches and finds my defconfig but then it ignores it. Where is my mistake?