From 1b22ef4a352bfc75e61bec3e059652434ed10654 Mon Sep 17 00:00:00 2001
From: Joerg Bornemann <joerg.bornemann@qt.io>
Date: Wed, 4 Sep 2024 09:52:15 +0200
Subject: [PATCH] configure: Add example how to pass CMake variables

Be more precise in how to pass CMake variables to configure.

Task-number: QTBUG-128424
Change-Id: I0f3e7d049fa861631587a4fb79e93be54319bbee
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
(cherry picked from commit 0a4d023e5fd2bd166503a27591c456991f680823)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
---
 config_help.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/config_help.txt b/config_help.txt
index ca7745c3285..33da4675773 100644
--- a/config_help.txt
+++ b/config_help.txt
@@ -2,9 +2,10 @@ Usage:  configure [options] [-- cmake-options]
 
 This is a convenience script for configuring Qt with CMake.
 Options after the double dash are directly passed to CMake.
-
-Configure understands variable assignments like VAR=value on the command line.
-These are passed to CMake as -DVAR=value.
+You can pass CMake variables as configure arguments:
+    configure VAR=value
+which is equivalent to
+    configure -- -DVAR=value
 
 Top-level installation directories:
   -prefix <dir> ...... The deployment directory, as seen on the target device.