From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 1/1] package/cmake: bump version to 4.3.1
Date: Thu, 2 Apr 2026 20:04:52 +0200 [thread overview]
Message-ID: <20260402180452.2780094-1-bernd@kuhls.net> (raw)
https://cmake.org/cmake/help/latest/release/4.3.html#id2
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
package/cmake/cmake.hash | 4 ++--
package/cmake/cmake.mk | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/cmake/cmake.hash b/package/cmake/cmake.hash
index 605bed2a40..5367ae2cd5 100644
--- a/package/cmake/cmake.hash
+++ b/package/cmake/cmake.hash
@@ -1,5 +1,5 @@
-# From https://cmake.org/files/v4.3/cmake-4.3.0-SHA-256.txt
-sha256 f51b3c729f85d8dde46a92c071d2826ea6afb77d850f46894125de7cc51baa77 cmake-4.3.0.tar.gz
+# From https://cmake.org/files/v4.3/cmake-4.3.1-SHA-256.txt
+sha256 0798f4be7a1a406a419ac32db90c2956936fecbf50db3057d7af47d69a2d7edb cmake-4.3.1.tar.gz
# Locally calculated
sha256 4382e7c1879ac90e3f101a395d23846fa4dbcaa1eed7265b43681e348754825d LICENSE.rst
diff --git a/package/cmake/cmake.mk b/package/cmake/cmake.mk
index 952e8174f4..4fdd294f5a 100644
--- a/package/cmake/cmake.mk
+++ b/package/cmake/cmake.mk
@@ -6,7 +6,7 @@
# When updating the version, please also update BR2_HOST_CMAKE_AT_LEAST_X_Y
CMAKE_VERSION_MAJOR = 4.3
-CMAKE_VERSION = $(CMAKE_VERSION_MAJOR).0
+CMAKE_VERSION = $(CMAKE_VERSION_MAJOR).1
CMAKE_SITE = https://cmake.org/files/v$(CMAKE_VERSION_MAJOR)
CMAKE_LICENSE = BSD-3-Clause
CMAKE_LICENSE_FILES = LICENSE.rst
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-04-02 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 18:04 Bernd Kuhls [this message]
2026-04-03 17:47 ` [Buildroot] [PATCH 1/1] package/cmake: bump version to 4.3.1 Julien Olivain via buildroot
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=20260402180452.2780094-1-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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