Merge patch series "tools: qconfig: print a proper error when database is missing"HEADmaster

Julien Stephan <jstephan@baylibre.com> says:

When I first ran ./tools/qconfig.py, it immediately crashed with a
Python traceback because the configuration database had not yet been
generated.

This series adds a simple pre-check that detects this condition and
prints a clear error message instructing the user to generate the
database first using the -b option, instead of failing with an unhandled
exception.

While looking at the script, I also noticed that the help text still
references the obsolete moveconfig.rst document. This series updates
that reference as well.

Link: https://lore.kernel.org/r/20260702-qconfig-check-for-db-v1-0-f0b96bf8fa44@baylibre.com

1 files changed, 5 insertions, 1 deletions

diff --git a/tools/qconfig.py b/tools/qconfig.py
index 5b85f9d22c3..930eb0e203d 100755
--- a/tools/qconfig.py
+++ b/tools/qconfig.py
@@ -871,6 +871,10 @@ def read_database():
                 value: set of boards using that option
 
     """
+    if not os.path.exists(CONFIG_DATABASE):
+        sys.exit(f"Error: database '{CONFIG_DATABASE}' not found. "
+                 f"Did you forget to generate it first with the -b option?")
+
     configs = {}
 
     # key is defconfig name, value is dict of (CONFIG_xxx, value)
@@ -1510,7 +1514,7 @@ def parse_args():
         cpu_count = 1
 
     epilog = '''Move config options from headers to defconfig files. See
-doc/develop/moveconfig.rst for documentation.'''
+doc/develop/qconfig.rst for documentation.'''
 
     parser = ArgumentParser(epilog=epilog)
     # Add arguments here