From decadba9c28e86de23e0ed3f5819c72a0f9ad3d9 Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Wed, 3 Oct 2018 20:26:29 +0200 Subject: Clarify --config-out description a bit --- README.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'README.rst') diff --git a/README.rst b/README.rst index 5316605..e4a9841 100644 --- a/README.rst +++ b/README.rst @@ -148,11 +148,12 @@ Make comment) in ``.config``, allowing them to be tested with ``ifdef`` in Make. If you make use of this, you might want to pass ``--config-out `` to -``genconfig`` and include the generated configuration file instead of including -``.config`` directly. This has the advantage that the generated configuration -file will always be a "full" configuration file, even if ``.config`` is -outdated. Otherwise, it might be necessary to run ``old(def)config`` or -``menuconfig`` before rebuilding with an outdated ``.config``. +``genconfig`` and include the configuration file it generates instead of +including ``.config`` directly. This has the advantage that the generated +configuration file will always be a "full" configuration file, even if +``.config`` is outdated. Otherwise, it might be necessary to run +``old(def)config`` or ``menuconfig`` before rebuilding with an outdated +``.config``. If you use ``--sync-deps`` to generate incremental build information, you can include ``deps/auto.conf`` instead, which is also a full configuration file. -- cgit v1.2.3