public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: u-boot@lists.denx.de
Subject: How to modify defconfig file - make savedefconfig?
Date: Thu, 27 Jan 2022 16:46:48 -0000 (UTC)	[thread overview]
Message-ID: <ssui9o$33b$1@ciao.gmane.io> (raw)

What is the "right" way to modify a defconfig file?

Most sources I've found just say things like "edit the defconfig
file". That seems error-prone -- especially when dealing with settings
that have side effects.

I did stumble across one mention of "make savedefconfig", and this
seems to be the right way to modify a defconfig file:

    make myboard_defconfig
    make menuconfig
    make savedefconfig
    cp defconfig configs/myboard_defconfig

Do people manually edit their defconfig file when they want to make a
change, or do they use "make savedefconfig" like I show above?

One reason I'm asking is that the original defconfig file provided by
the silicon vendor (Renesas) appears to be a manually stripped-down
..config file, because when I do

   make vendors_defconfig
   make savedefconfig

The defconfig file generated by 'make savedefconfig' looks _nothing_
like the starting vendors_defconfig. The new defconfig generates the
same .config file as the vendors_defconfig file. But the
vendors_defconfig file is arranged completely differently with
different/extra comments, extra blank lines, etc.

--
Grant




             reply	other threads:[~2022-01-27 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 16:46 Grant Edwards [this message]
2022-01-28 10:26 ` How to modify defconfig file - make savedefconfig? Alexander Dahl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ssui9o$33b$1@ciao.gmane.io' \
    --to=grant.b.edwards@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox