From abd08a0cb52db13c6c6403d5a3793c2fa0e062b6 Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Wed, 3 Oct 2018 04:58:27 +0200 Subject: Clarify '# CONFIG_FOO is not set' in how-to --- README.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index 6b6808b..3c38839 100644 --- a/README.rst +++ b/README.rst @@ -142,8 +142,9 @@ Using ``.config`` files as Make input ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ``.config`` files use Make syntax and can be included directly in Makefiles to -read configuration values from there. This is why unset values are written out -as ``# CONFIG_FOO is not set`` (a Make comment) in ``.config``. +read configuration values from there. This is why ``n``-valued ``bool``/``tristate`` +values are written out as ``# CONFIG_FOO is not set`` (a Make comment) in ``.config`` +(allowing them to be tested with ``ifdef`` in Make). If you make use of this, you might want to pass ``--sync-deps`` to ``genconfig`` and include ``deps/auto.conf`` in your Makefiles instead of -- cgit v1.2.3