Creating a configuration fragment is currently done by saving off the current .config, running makemenuconfig, then taking the diff of the old and new .config, pruning the junk, and saving off a .cfg fragment. Seems this could easily be done as a bitbake task which: 1. depends on kernel_configme 2. saves off the .config as config.orig 3. runs makemenuconfig 4. creates a diff and saves as fragment.cfg 5. restores config.orig to .config 6. places fragment.cfg in the working dir 7. does not reset the stamps for tasks after kernel_configme if kernel_configme didn't need to be run.
Hi, I have a working patch to this. But I have one question. Is the menuconfig task creates a fragment.cfg? or is better the user first call menuconfig task, does the configuration and then call fragmentconfig task? Like this: bitbake -c menuconfig liux-yocto bitbake -c fragmentconfig liux-yocto Thanks.
Created attachment 1746 [details] Add fragmentconfig Proposed patch to cml1
Created attachment 1747 [details] Add fragmentconfig task Proposed patch to kernel-yocto.
Created attachment 1750 [details] kernel-dev manual updated Updated kernel-dev manual.
Hi, Merged on master: yocto-docs: 5b7ccdbf708cbeebc2d8dc91db129fb35aabdcdd openembedded-core: 5b7ccdbf708cbeebc2d8dc91db129fb35aabdcdd, db2a44c8f08f2371a52ff6662d6bc64bc42ad551