From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] host-cmake: Version bump. 3.31.8 -> 4.5.0
Date: Tue, 17 Nov 2026 21:46:01 +0100 [thread overview]
Message-ID: <20261117204601.1256209-1-christian.melki@t2data.com> (raw)
I revisited my rejection of 4.0 a while ago.
Seems to work better now. As usualy, ymmv. Works for me.
https://cmake.org/cmake/help/latest/release/3.31.html
https://cmake.org/cmake/help/latest/release/4.0.html
https://cmake.org/cmake/help/latest/release/4.1.html
https://cmake.org/cmake/help/latest/release/4.2.html
https://cmake.org/cmake/help/latest/release/4.3.html
https://cmake.org/cmake/help/latest/release/4.4.html
https://cmake.org/cmake/help/latest/release/4.5.html
* Various utility library changed license file hash.
Nothing major and it looks like all was updated from the
upstream.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/host-cmake.make | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/rules/host-cmake.make b/rules/host-cmake.make
index 5336e7a32..932f15661 100644
--- a/rules/host-cmake.make
+++ b/rules/host-cmake.make
@@ -15,8 +15,8 @@ HOST_PACKAGES-$(PTXCONF_HOST_CMAKE) += host-cmake
#
# Paths and names
#
-HOST_CMAKE_VERSION := 3.31.8
-HOST_CMAKE_SHA256 := e3cde3ca83dc2d3212105326b8f1b565116be808394384007e7ef1c253af6caa
+HOST_CMAKE_VERSION := 4.5.0
+HOST_CMAKE_SHA256 := 424352d6133e8455e020da787008e8dc67abb18820af3532572ab35657e49213
HOST_CMAKE := cmake-$(HOST_CMAKE_VERSION)
HOST_CMAKE_SUFFIX := tar.gz
HOST_CMAKE_URL := https://cmake.org/files/v$(basename $(HOST_CMAKE_VERSION))/$(HOST_CMAKE).$(HOST_CMAKE_SUFFIX)
@@ -24,16 +24,16 @@ HOST_CMAKE_SOURCE := $(SRCDIR)/$(HOST_CMAKE).$(HOST_CMAKE_SUFFIX)
HOST_CMAKE_DIR := $(HOST_BUILDDIR)/$(HOST_CMAKE)
HOST_CMAKE_LICENSE := 0BSD AND BSD-2-Clause AND BSD-3-Clause AND Apache-2.0 AND bzip2-1.0.6 AND (MIT OR public_domain) AND MIT AND curl
HOST_CMAKE_LICENSE_FILES := \
- file://Copyright.txt;md5=718f05155941b33862726348d3cd46ce \
+ file://LICENSE.rst;md5=69baa2b64b4976226122f87ecbad32c5 \
file://Source/kwsys/Copyright.txt;md5=64ed5ec90b0f9868cf0b08ea5b954dfe \
file://Utilities/KWIML/Copyright.txt;md5=bdc657917a0eec5751b3d5eafd4b413c \
file://Utilities/cmbzip2/LICENSE;md5=1e5cffe65fc786f83a11a4b225495c0b \
- file://Utilities/cmcurl/COPYING;md5=eed2e5088e1ac619c9a1c747da291d75 \
- file://Utilities/cmexpat/COPYING;md5=7b3b078238d0901d3b339289117cb7fb \
+ file://Utilities/cmcurl/COPYING;md5=0515352b285b9c3f66464b135c9c0fdc \
+ file://Utilities/cmexpat/COPYING;md5=f4fedd6116da0e171f7cb4d2923d7ac2 \
file://Utilities/cmjsoncpp/LICENSE;md5=5d73c165a0f9e86a1342f32d19ec5926 \
- file://Utilities/cmlibarchive/COPYING;md5=d499814247adaee08d88080841cb5665 \
+ file://Utilities/cmlibarchive/COPYING;md5=7ce08437ff7f5e24d72e666313ae4084 \
file://Utilities/cmlibrhash/COPYING;md5=a8c2a557a5c53b1c12cddbee98c099af \
- file://Utilities/cmlibuv/LICENSE;md5=ad93ca1fffe931537fcf64f6fcce084d \
+ file://Utilities/cmlibuv/LICENSE;md5=74b6f2f7818a4e3a80d03556f71b129b \
file://Utilities/cmnghttp2/COPYING;md5=764abdf30b2eadd37ce47dcbce0ea1ec \
file://Utilities/cmzlib/Copyright.txt;md5=2450bdbf9b528e25d3c4dab22d3595fe \
file://Utilities/cmzstd/LICENSE;md5=0822a32f7acdbe013606746641746ee8
--
2.43.0
reply other threads:[~2026-11-17 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261117204601.1256209-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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