Kernel Newbies archive mirror
 help / color / mirror / Atom feed
From: Richard <richard_siegfried@systemli.org>
To: kernelnewbies@kernelnewbies.org
Subject: olddefconfig vs. menuconfig (just open, save file and close)
Date: Sat, 15 Oct 2022 19:22:17 +0200	[thread overview]
Message-ID: <b306ce01-2e08-791e-57c4-90248d27b540@systemli.org> (raw)

Hi all,

When you have an existing .config and just open `make menuconfig` say 
close and save the file you end up with a working (for compilation) 
.config file.

As you do when you use make olddefconfig.

In a recent (arm) project I have noticed that the .config files produced 
in the two cases differ (when starting from the same base .config). In 
general menuconfig adds more options (lines) than olddefconfig.

What is the difference between the two cases? When should I use 
olddefconfig, when should I use the menuconfig approach?

Thanks,
-- Richard

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

                 reply	other threads:[~2022-10-15 17:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=b306ce01-2e08-791e-57c4-90248d27b540@systemli.org \
    --to=richard_siegfried@systemli.org \
    --cc=kernelnewbies@kernelnewbies.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).