public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org, kde@gentoo.org, base-system@gentoo.org
Subject: [gentoo-dev] [PATCH 2/5] cmake.eclass: Introduce _CMAKE_MINREQVER_UNSUPPORTED
Date: Sun, 15 Jun 2025 22:30:55 +0200	[thread overview]
Message-ID: <2235940.irdbgypaU6@tuxbrain.fritz.box> (raw)
In-Reply-To: <12693580.O9o76ZdvQC@tuxbrain.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

Allows to split detection/eqawarn and applying cmakearg over different
phases.

Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
---
 eclass/cmake.eclass | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/eclass/cmake.eclass b/eclass/cmake.eclass
index ea5a769b4cb4..4104882005a3 100644
--- a/eclass/cmake.eclass
+++ b/eclass/cmake.eclass
@@ -123,6 +123,11 @@ fi
 # If set, skip detection of CMakeLists.txt unsupported in CMake 4 in case of
 # false positives (e.g. unused outdated bundled libs).
 
+# @ECLASS_VARIABLE: _CMAKE_MINREQVER_UNSUPPORTED
+# @DEFAULT_UNSET
+# @DESCRIPTION:
+# Is set to true if an unsupported cmake_minimum_required value was detected.
+
 # @ECLASS_VARIABLE: CMAKE_QA_SRC_DIR_READONLY
 # @USER_VARIABLE
 # @DEFAULT_UNSET
@@ -455,7 +460,7 @@ cmake_src_configure() {
 	# Fix xdg collision with sandbox
 	xdg_environment_reset
 
-	local file ver cmreq_isold
+	local file ver
 	if ! [[ ${CMAKE_QA_COMPAT_SKIP} ]]; then
 		while read -d '' -r file ; do
 			ver=$(sed -ne "/cmake_minimum_required/I{s/.*\(\.\.\.*\|\s\)\([0-9.]*\)\([)]\|\s\).*$/\2/p;q}" \
@@ -463,7 +468,7 @@ cmake_src_configure() {
 			)
 
 			if [[ -n $ver ]] && ver_test $ver -lt "3.5"; then
-				cmreq_isold=true
+				_CMAKE_MINREQVER_UNSUPPORTED=true
 			fi
 		done < <(find "${CMAKE_USE_DIR}" -type f -iname "CMakeLists.txt" -print0)
 	fi
@@ -648,7 +653,7 @@ cmake_src_configure() {
 		cmakeargs+=( -C "${CMAKE_EXTRA_CACHE_FILE}" )
 	fi
 
-	if [[ ${cmreq_isold} ]]; then
+	if [[ ${_CMAKE_MINREQVER_UNSUPPORTED} ]]; then
 		eqawarn "QA Notice: Compatibility with CMake < 3.5 has been removed from CMake 4,"
 		eqawarn "${CATEGORY}/${PN} will fail to build w/o a fix."
 		eqawarn "See also tracker bug #951350; check existing bug or file a new one for"
-- 
2.49.0


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 789 bytes --]

  reply	other threads:[~2025-06-15 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15 20:26 [gentoo-dev] [PATCH 1/5] cmake.eclass: Improve _cmake_modify-cmakelists(), consolidate the sed Andreas Sturmlechner
2025-06-15 20:30 ` Andreas Sturmlechner [this message]
2025-06-15 20:31 ` [gentoo-dev] [PATCH 3/5] cmake.eclass: mv _CMAKE_MINREQVER_UNSUPPORTED detection to src_prepare Andreas Sturmlechner
2025-06-15 20:31 ` [gentoo-dev] [PATCH 4/5] cmake.eclass: Avoid none-detection by ensuring match starts w/ digit Andreas Sturmlechner
2025-06-15 20:31 ` [gentoo-dev] [PATCH 5/5] cmake.eclass: Add src_install() check for CMake-4-incompatible modules Andreas Sturmlechner
2025-06-16  5:19 ` [gentoo-dev] [PATCH 1/5] cmake.eclass: Improve _cmake_modify-cmakelists(), consolidate the sed Ulrich Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2235940.irdbgypaU6@tuxbrain.fritz.box \
    --to=asturm@gentoo.org \
    --cc=base-system@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=kde@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox