mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] host-cmake: Version bump 3.23.1 -> 3.25.0
Date: Tue, 22 Nov 2022 10:42:33 +0100	[thread overview]
Message-ID: <20221122094233.3576796-1-christian.melki@t2data.com> (raw)

Release notes, somewhat readable:
https://cmake.org/cmake/help/v3.24/release/3.24.html
https://cmake.org/cmake/help/v3.25/release/3.25.html

A bunch of changes, seems to build fine for me.
I found this one to be interesting:
https://cmake.org/cmake/help/v3.24/policy/CMP0132.html#policy:CMP0132

Changes to license files:
* Copyright.txt: Dates and versions, contributor list.
* Utilities/cmcurl/COPYING: Date changes.
* Utilities/cmzlib/Copyright.txt: Date and version changes.

Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
 rules/host-cmake.make | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/rules/host-cmake.make b/rules/host-cmake.make
index 44d43fbe5..305e90d87 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.23.1
-HOST_CMAKE_MD5		:= b0d46fdcca030372f0a464146243e193
+HOST_CMAKE_VERSION	:= 3.25.0
+HOST_CMAKE_MD5		:= a9d079eaf3f91ed9898834afb24e2b17
 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,18 +24,18 @@ 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=f2102a52df7aa592cf072180e7ebc8c7 \
+	file://Copyright.txt;md5=09069e0fffe4e5eaf6dde04c3b1932e5 \
 	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=425f6fdc767cc067518eef9bbdf4ab7b \
+	file://Utilities/cmcurl/COPYING;md5=190c514872597083303371684954f238 \
 	file://Utilities/cmexpat/COPYING;md5=9e2ce3b3c4c0f2670883a23bbd7c37a9 \
 	file://Utilities/cmjsoncpp/LICENSE;md5=5d73c165a0f9e86a1342f32d19ec5926 \
 	file://Utilities/cmlibarchive/COPYING;md5=d499814247adaee08d88080841cb5665 \
 	file://Utilities/cmlibrhash/COPYING;md5=a8c2a557a5c53b1c12cddbee98c099af \
 	file://Utilities/cmlibuv/LICENSE;md5=ad93ca1fffe931537fcf64f6fcce084d \
 	file://Utilities/cmnghttp2/COPYING;md5=764abdf30b2eadd37ce47dcbce0ea1ec \
-	file://Utilities/cmzlib/Copyright.txt;md5=20549c31f1fec4df39b48732d8802c2a \
+	file://Utilities/cmzlib/Copyright.txt;md5=e08ebeaec41728215e9137e1d2b4d7cd \
 	file://Utilities/cmzstd/LICENSE;md5=c7f0b161edbe52f5f345a3d1311d0b32
 
 
-- 
2.34.1




             reply	other threads:[~2022-11-22  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22  9:42 Christian Melki [this message]
2022-11-23  6:55 ` Michael Olbrich
2022-12-05  8:29   ` Michael Olbrich
2022-12-05 12:53 ` [ptxdist] [APPLIED] " Michael Olbrich

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=20221122094233.3576796-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