[Buildroot] Development flow to track .config

[Ramon Crichlow]

Didn't know about make savedefconfig - thanks!

Ramon

On Tue, Jan 31, 2023 at 3:36 PM Edgar Bonet <bonet at grenoble.cnrs.fr> wrote:

> Hello!
>
> Ramon Crichlow wrote:
> > Is the following flow best practice?  If not please suggest a better one.
> >
> > 1.  Make a change to .config using make menuconfig
> > 2.  Diff the change between .config and .config.old
> > 3.  Edit abc_defconfig to mirror the changes in step 2
> > 4.  Commit abc_defconfig
>
> Not sure it's the best, but here is what I do:
>
> 1. git switch -c 'my-custom-branch'
> 2. make some_board_defconfig
> 3. make nconfig # or your preferred variant of menuconfig, save and exit
> 4. make savedefconfig # this will save the relevant changes to
> some_board_defconfig
> 5. git commit -a -m 'My custom changes to some_board_defconfig'
>
> Best regards,
>
> Edgar.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20230131/9b25d17e/attachment-0001.html>