From 841ab04973a1f42cfafea41835bb8d09df15dbd6 Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Wed, 22 May 2019 09:03:21 +0200 Subject: Mention that .config can be brought up-to-date via menuconfig/guiconfig Good to know. --- README.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.rst b/README.rst index 2a80f9b..36fbd1e 100644 --- a/README.rst +++ b/README.rst @@ -158,7 +158,10 @@ Getting started 5. To update an old ``.config`` file after the Kconfig files have changed (e.g. to add new options), run ``oldconfig`` (prompts for values for new options) - or ``olddefconfig`` (gives new options their default value). + or ``olddefconfig`` (gives new options their default value). Entering the + ``menuconfig`` or ``guiconfig`` interface and saving the configuration will + also update it (the configuration interfaces always prompt for saving + on exit if it would modify the contents of the ``.config`` file). Due to Kconfig semantics, simply loading an old ``.config`` file performs an implicit ``olddefconfig``, so building will normally not be affected by -- cgit v1.2.3