[ANNOUNCE] CMake 3.28.0-rc1 is ready for testing
I am proud to announce the first CMake 3.28 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.28
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.28/release/3.28.html
Some of the more significant changes in CMake 3.28 are:
* C++ 20 named modules are now supported by Ninja Generators and
Visual Studio Generators for VS 2022 and newer, in combination with
the MSVC 14.34 toolset (provided with VS 17.4) and newer, LLVM/Clang
16.0 and newer, and GCC 14 (after the 2023-09-20 daily bump) and
newer. See "cmake-cxxmodules(7)" for details.
* "HIP" language code may now be compiled for NVIDIA GPUs using the
NVIDIA CUDA Compiler (NVCC). See the "CMAKE_HIP_PLATFORM" variable.
* On Apple platforms, ".xcframework" folders are now supported.
* The "exec_program()" command, which has been deprecated since CMake
3.0, has been removed by policy "CMP0153". Use the
"execute_process()" command instead.
* Generated files, in targets using File Sets, are now considered
private by default. Generated public headers must be specified
using file sets. This allows Ninja Generators to produce more
efficient build graphs. See policy "CMP0154".
* The "find_library()", "find_path()", and "find_file()" commands no
longer search in installation prefixes derived from the "PATH"
environment variable. This behavior was added in CMake 3.3 to
support MSYS and MinGW ("MSYSTEM") development environments on
Windows, but it can search undesired prefixes that happen to be in
the "PATH" for unrelated reasons. Users who keep some
"/bin" directories in the "PATH" just for their tools do not
necessarily want any corresponding "/lib" or
"/include" directories searched. The behavior was reverted
for non-Windows platforms by CMake 3.6. Now it has been reverted on
Windows platforms too.
CMake 3.28 Release Notes
Changes made since CMake 3.27 include the following.
New Features
Languages
-
* C++ 20 named modules are now supported by Ninja Generators and
Visual Studio Generators for VS 2022 and newer, in combination with
the MSVC 14.34 toolset (provided with VS 17.4) and newer, LLVM/Clang
16.0 and newer, and GCC 14 (after the 2023-09-20 daily bump) and
newer. See "cmake-cxxmodules(7)" for details.
* "HIP" language code may now be compiled for NVIDIA GPUs using the
NVIDIA CUDA Compiler (NVCC). See the "CMAKE_HIP_PLATFORM" variable.
Platforms
-
* On Apple platforms, ".xcframework" folders are now supported:
* The "find_library()" command now finds ".xcframework" folders.
* The "target_link_libraries()" command now supports linking against
a ".xcframework" folder.
* The "IMPORTED_LOCATION" target property of an imported library
target may now be the path to a ".xcframework" folder.
* Apple visionOS and its "xros" and "xrsimulator" SDKs are now
supported. Compiling for Apple visionOS can be requested by setting
"CMAKE_SYSTEM_NAME" to "visionOS". See Cross Compiling for iOS,
tvOS, visionOS, or watchOS for more information.
Presets
---
* "cmake-presets(7)" files now support schema version "8". It adds
support for a "$schema" field.
Compilers
-
* Cray Clang-based compilers are now supported with "compiler id"
"CrayClang".
* The OrangeC compiler is now supported with "compiler id" "OrangeC".
Commands
* The "add_custom_command()" and "add_custom_target()" commands gained
a "JOB_SERVER_AWARE" option.
* The "cmake_host_system_information()" command gained a
"MSYSTEM_PREFIX" query for the installation prefix of a MSYS or
MinGW development environment on Windows hosts.
* The "set_property()" command "TEST" mode gained a "DIRECTORY" option
to set properties on tests in other directories.
* The "set_tests_properties()" command gained a "DIRECTORY" option to
set properties on tests in other directories.
* The "get_property()" command "TEST" mode gained a "DIRECTORY" option
to get properties on tests in other directories.
* The "get_test_property()" command gained a "DIRECTORY" option to get
properties on tests in other directories.
Variables
-
* The "CMAKE_CROSSCOMPILING_EMULATOR" environment variable was added
to initialize the "CMAKE_CROSSCOMPILING_EMULATOR" cache variable.
* The "CMAKE_HIP_PLATFORM" variable was added to specify the GPU
platform for which HIP language sources are to be compiled ("amd" or
"nvidia").
Properties
--
* On imported shared libraries, the "IMPORTED_IMPLIB" target property
may now be used without "IMPORTED_LOCATION". This can be used to
represent a stub library whose location should not be added as a
runtime search path to dependents that link it.
* The "IMPORTED_LOCATION" property of a macOS framework may now be a
path to the ".framework" folder itself.
* The "XCODE_EMBED_RESOURCES" target property was
Re: KDE Gear projects with failing CI (release/23.08) (10 October 2023)
On Thu, Oct 12, 2023 at 2:35 AM Albert Astals Cid wrote: > El dimecres, 11 d’octubre de 2023, a les 12:03:56 (CEST), Ben Cooksley va > escriure: > > On Wed, Oct 11, 2023 at 4:45 PM Albert Astals Cid wrote: > > > Please work on fixing them, otherwise i will remove the failing CI > > > jobs on their 4th failing week, it is very important that CI is passing > > > for > > > multiple reasons. > > > > > > Bad news: We have lots of more repositories failing :/ But they are all > > > flatpak, so not that terrible. Please see last weeks' discussion as to > a > > > proposed solution if you have time to work on it. > > > > > > = FAILING TO COMPILE = > > > > > > kamoso: > > > * https://invent.kde.org/multimedia/kamoso/-/pipelines/497748 > > > > > > * suse is failing to find packages > > > > > >* some gstreamer packages need to be added to the CI image? > > > > Should be fixed shortly. > > Could it be that you installed the wrong thing? Seems to still be failing > > What we need AFAICS is gstreamer-plugins-base-devel > Nope, the image build hadn't been triggered, which i've now done. Note that for anyone looking at porting to Qt 6 we can't rebuild that image for the moment as SUSE is bumping up to Qt 6.6, which will end up being a separate Docker image entirely. Once they've finished building it I will start the bumping process (which starts by building a new Docker image, then seeding the package registry, then finally switching CI over - so please try to avoid making SIC/BIC changes for the next week or so) > > Cheers, > Albert > > > Cheers, Ben
Re: Fwd: KDE Craft Blueprints | Failed pipeline for master | 03023ae7
This broke due to the switch to python 3.12 which removed several deprecated functions Craft still used. It is fixed now. Cheers, Julius 06.10.2023 01:08:10 Michael Reeves : > Craft blueprints testing is failing for craft internal reasons. > > -- Forwarded message - > From: *KDE Invent* > Date: Thu, Oct 5, 2023 at 6:58 PM > Subject: KDE Craft Blueprints | Failed pipeline for master | 03023ae7 > To: > > > > [https://invent.kde.org/uploads/-/system/appearance/header_logo/1/kde-logo-white-blue-128x128.png] > > [https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-x-red-inverted-06e39ba2a7f9a32f6201e420175db85a4b6ac0348203fdc069001b440149.gif][✖][https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-x-red-inverted-06e39ba2a7f9a32f6201e420175db85a4b6ac0348203fdc069001b440149.gif]Pipeline > #493762 has failed! > > > Project Packaging [https://invent.kde.org/packaging]/ KDE Craft > Blueprints[https://invent.kde.org/packaging/craft-blueprints-kde] > > Branch > [https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-branch-gray-53618a7fc19d4d32ccbabac2f6d59bebe67202a9f2f1255e3f72c69756c0dd9c.gif]master[https://invent.kde.org/packaging/craft-blueprints-kde/-/commits/master] > > > Commit > [https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-commit-gray-c10243ac24cde64b549aec91de35e6b49c8739b506b86472b54614c10d8b4aac.gif]03023ae7[https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/03023ae74c1273ec06757d56732d39bf9a611c62] > [kdiff3] Fix blacklist syntax > > > Commit Author > [http:///assets/no_avatar-849f9c04a3a0d0cea2424ae97b27447dc64a7dbfae83c036c45b403392f0e8ba.png]Michael > Reeves[https://invent.kde.org/mreeves] > > Pipeline > #493762[https://invent.kde.org/packaging/craft-blueprints-kde/-/pipelines/493762] > triggered by > [http:///assets/no_avatar-849f9c04a3a0d0cea2424ae97b27447dc64a7dbfae83c036c45b403392f0e8ba.png]Michael > Reeves[https://invent.kde.org/mreeves] > had 1 failed job > > Failed job > > [https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-x-red-67056b7b99899e30453df79abfbe16162f6a26ed789d8236f81afcaea216ffe6.gif][✖][https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-x-red-67056b7b99899e30453df79abfbe16162f6a26ed789d8236f81afcaea216ffe6.gif]test > > run-tests[https://invent.kde.org/packaging/craft-blueprints-kde/-/jobs/1234242] > > > > [https://invent.kde.org/assets/mailers/gitlab_logo_black_text-5430ca955baf2bbce6d3aa856a025da70ac5c9595597537254f665c10beab7a5.png][GitLab][https://invent.kde.org/assets/mailers/gitlab_logo_black_text-5430ca955baf2bbce6d3aa856a025da70ac5c9595597537254f665c10beab7a5.png] > You're receiving this email because of your account on > invent.kde.org[https://invent.kde.org]. Manage all > notifications[https://invent.kde.org/-/profile/notifications] · > Help[https://invent.kde.org/help] > > >
Re: KDE Gear projects with failing CI (release/23.08) (10 October 2023)
El dimecres, 11 d’octubre de 2023, a les 12:03:56 (CEST), Ben Cooksley va escriure: > On Wed, Oct 11, 2023 at 4:45 PM Albert Astals Cid wrote: > > Please work on fixing them, otherwise i will remove the failing CI > > jobs on their 4th failing week, it is very important that CI is passing > > for > > multiple reasons. > > > > Bad news: We have lots of more repositories failing :/ But they are all > > flatpak, so not that terrible. Please see last weeks' discussion as to a > > proposed solution if you have time to work on it. > > > > = FAILING TO COMPILE = > > > > kamoso: > > * https://invent.kde.org/multimedia/kamoso/-/pipelines/497748 > > > > * suse is failing to find packages > > > >* some gstreamer packages need to be added to the CI image? > > Should be fixed shortly. Could it be that you installed the wrong thing? Seems to still be failing What we need AFAICS is gstreamer-plugins-base-devel Cheers, Albert
Re: KDE Gear projects with failing CI (master) (10 October 2023)
On 10/11/23 11:52, Ben Cooksley wrote: On Wed, Oct 11, 2023 at 4:37 PM Albert Astals Cid wrote: Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: We have 3 new repositories failing = FAILING UNIT TESTS = kate: * https://invent.kde.org/utilities/kate/-/pipelines/497698 * tests are failing This looks to be a regression within KConfig no? Likely won't show up on a developer system as the tests are bailing out on asserts (the CI system builds a full Debug build on all platforms except Windows, with all the consequences of that - this being one of them) See https://invent.kde.org/frameworks/kconfig/-/merge_requests/232 cantor: * https://invent.kde.org/education/cantor/-/pipelines/497702 * flatpak is failing * Probably needs to be disbled until we have a KF6 capable flatpak? Flatpak should be removed from applications that have gone Qt 6 only yes. kamoso: * https://invent.kde.org/multimedia/kamoso/-/pipelines/497706 * suse is failing to find packages * some gstreamer packages need to be added to the CI image? Will be fixed once I have the image rebuild completed. Cheers, Albert Thanks, Ben
Re: KDE Gear projects with failing CI (release/23.08) (10 October 2023)
On Wed, Oct 11, 2023 at 4:45 PM Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI > jobs on their 4th failing week, it is very important that CI is passing > for > multiple reasons. > > Bad news: We have lots of more repositories failing :/ But they are all > flatpak, so not that terrible. Please see last weeks' discussion as to a > proposed solution if you have time to work on it. > > = FAILING TO COMPILE = > > kamoso: > * https://invent.kde.org/multimedia/kamoso/-/pipelines/497748 > * suse is failing to find packages >* some gstreamer packages need to be added to the CI image? > Should be fixed shortly. > > > = FAILING UNIT TESTS = > > konsole: (4th week) > * https://invent.kde.org/utilities/konsole/-/pipelines/497709 > * freebsd_qt515 tests are still failing. I will be disabling them > I have removed the failing line of code which has fixed 1/2 of the tests. The remaining DBus test will have to be fixed by a Konsole developer i'm afraid, however I imagine "Program to run not set." may explain it in part. > > kate: > * https://invent.kde.org/utilities/kate/-/pipelines/497708 > * tests are failing > See my other mail - looks like Kate is just collateral damage. > > > = FLATPAK FAILING = > > We kind of maybe have a plan for that, but needs executing. Since no one > has > executed it and some of the tests are failing for the whole week i will be > commenting them all out > > cantor > kalgebra > bomber > bovo > kapman > katomic > kblackbox > kblocks > kbounce > kbreakout > kdiamond > kfourinline > kgoldrunner > kigo > killbots > kiriki > kjumpingcube > klickety > klines > kmahjongg > kmines > knavalbattle > knetwalk > kolf > kollision > Sounds reasonable to me, for Qt 6 only applications at least. Flatpak is not yet ready to make the jump to Qt 6. Cheers, Ben
Re: KDE Gear projects with failing CI (master) (10 October 2023)
On Wed, Oct 11, 2023 at 4:37 PM Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI > jobs on their 4th failing week, it is very important that CI is passing > for > multiple reasons. > > Bad news: We have 3 new repositories failing > > = FAILING UNIT TESTS = > > kate: > * https://invent.kde.org/utilities/kate/-/pipelines/497698 > * tests are failing > This looks to be a regression within KConfig no? Likely won't show up on a developer system as the tests are bailing out on asserts (the CI system builds a full Debug build on all platforms except Windows, with all the consequences of that - this being one of them) > > cantor: > * https://invent.kde.org/education/cantor/-/pipelines/497702 > * flatpak is failing >* Probably needs to be disbled until we have a KF6 capable flatpak? > Flatpak should be removed from applications that have gone Qt 6 only yes. > > kamoso: > * https://invent.kde.org/multimedia/kamoso/-/pipelines/497706 > * suse is failing to find packages >* some gstreamer packages need to be added to the CI image? > > Will be fixed once I have the image rebuild completed. > > > Cheers, > Albert > Thanks, Ben
[sysadmin/ci-images] /: Include more of GStreamer to ensure Kamoso has it's dependencies installed.
Git commit 3994445c7dc82b9011adcb2d7ccc901320978963 by Ben Cooksley. Committed on 11/10/2023 at 11:51. Pushed by bcooksley into branch 'master'. Include more of GStreamer to ensure Kamoso has it's dependencies installed. CCMAIL: kde-devel@kde.org M +1-0suse-qt515/Dockerfile M +1-0suse-qt65/Dockerfile https://invent.kde.org/sysadmin/ci-images/-/commit/3994445c7dc82b9011adcb2d7ccc901320978963 diff --git a/suse-qt515/Dockerfile b/suse-qt515/Dockerfile index 4a6d266..09ae593 100755 --- a/suse-qt515/Dockerfile +++ b/suse-qt515/Dockerfile @@ -303,6 +303,7 @@ RUN zypper --non-interactive in --allow-vendor-change \ pcre-devel \ # xdg-portal-test-kde gstreamer-devel \ +gstreamermm-devel \ # Haruna mpv-devel \ # kscreenlocker diff --git a/suse-qt65/Dockerfile b/suse-qt65/Dockerfile index 03fc442..9ed9748 100644 --- a/suse-qt65/Dockerfile +++ b/suse-qt65/Dockerfile @@ -304,6 +304,7 @@ RUN zypper --non-interactive in --allow-vendor-change \ aqbanking-devel \ # xdg-portal-test-kde gstreamer-devel \ +gstreamermm-devel \ # Haruna mpv-devel \ # kscreenlocker
