[ANNOUNCE] CMake 3.29.0-rc3 is ready for testing
I am proud to announce the third CMake 3.29 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.29
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.29/release/3.29.html
Release milestone is available at:
https://gitlab.kitware.com/cmake/cmake/-/milestones/136
Some of the more significant changes in CMake 3.29 are:
* The LLVM/Clang GNU-like frontend on Windows ("clang++") may now be
used to compile "CUDA" language sources.
* TI Clang-based compilers are now supported with compiler id
"TIClang".
* The "cmake_language(EXIT)" sub-command was added to terminate "cmake
-P" scripts with a specified exit code.
* The "export(SETUP)" sub-command was added to configure export sets.
Its "PACKAGE_DEPENDENCY" option configures how "find_dependency()"
calls are exported. Its "TARGET" option's "XCFRAMEWORK_LOCATION"
setting specifies the location of a ".xcframework" that can be
substituted for an installed target.
* "install(EXPORT)" and "export(EXPORT)" learned a new
"EXPORT_PACKAGE_DEPENDENCIES" argument, which can be used to
generate "find_dependency()" calls based on what targets the
exported targets depend on.
* The "CMAKE_LINKER_TYPE" variable and corresponding "LINKER_TYPE"
target property were added to specify what linker to use with some
toolchains.
* A "CMAKE_TEST_LAUNCHER" variable and corresponding "TEST_LAUNCHER"
target property were added to specify a launcher to be used by
executable targets when invoked by tests added by the "add_test()"
command.
CMake 3.29 Release Notes
Changes made since CMake 3.28 include the following.
New Features
Command-Line
* "cmake(1)" "-E cat" can now print the standard input by passing the
"-" argument.
Generators
--
* Visual Studio Generators now support selecting between the Intel
oneAPI Fortran compiler ("ifx") and the Intel classic Fortran
compiler ("ifort") using a "fortran=" field in
"CMAKE_GENERATOR_TOOLSET".
File-Based API
--
* The "cmake-file-api(7)" "codemodel" version 2 "version" field has
been updated to 2.7.
* The "cmake-file-api(7)" "codemodel" version 2 "target" object gained
a new "launchers" field.
Compilers
-
* The LLVM/Clang GNU-like frontend on Windows ("clang++") may now be
used to compile "CUDA" language sources.
* Compilers targeting the GNU ABI on Windows (MinGW) may now be used
to compile Objective C ("OBJC") and Objective C++ ("OBJCXX"). These
include GNU compilers ("gcc" and "g++") and the LLVM/Clang GNU-like
frontends ("clang" and "clang++").
* TI Clang-based compilers are now supported with compiler id
"TIClang".
Commands
* The add_custom_command(TARGET) signature now supports adding build
events through Alias Targets.
* The "cmake_language(EXIT)" sub-command was added to terminate "cmake
-P" scripts with a specified exit code.
* The "export(SETUP)" sub-command was added to configure export sets.
Its "PACKAGE_DEPENDENCY" option configures how "find_dependency()"
calls are exported. Its "TARGET" option's "XCFRAMEWORK_LOCATION"
setting specifies the location of a ".xcframework" that can be
substituted for an installed target.
* The "if()" command gained new tests "IS_READABLE", "IS_WRITABLE" and
"IS_EXECUTABLE" to check file or directory permissions.
* "install(EXPORT)" and "export(EXPORT)" learned a new
"EXPORT_PACKAGE_DEPENDENCIES" argument, which can be used to
generate "find_dependency()" calls based on what targets the
exported targets depend on.
Variables
-
* The "CMAKE_INSTALL_PREFIX" environment variable was added to provide
a default value for the "CMAKE_INSTALL_PREFIX" variable.
* The "CMAKE_LINKER_TYPE" variable and corresponding "LINKER_TYPE"
target property were added to specify what linker to use with some
toolchains.
* The "CMAKE__COMPILER_LINKER",
"CMAKE__COMPILER_LINKER_ID",
"CMAKE__COMPILER_LINKER_VERSION" and
"CMAKE__COMPILER_LINKER_FRONTEND_VARIANT" variables were added
to describe the linker used by the language's link step.
* The "CMAKE_PROJECT_INCLUDE", "CMAKE_PROJECT_INCLUDE_BEFORE",
"CMAKE_PROJECT__INCLUDE", and "CMAKE_PROJECT__INCLUDE_BEFORE" variables learned to support a semicolon-
separated list of CMake language files to be included sequentially.
These variables can also reference module names to be found in
"CMAKE_MODULE_PATH" or builtin to CMake.
* The "CMAKE_SKIP_TEST_ALL_DEPENDENCY" variable was added to control
whether the "test" (or "RUN_TESTS") buildsystem target depends on
the "all" (or "ALL_BUILD") target.
* A "CMAKE_TEST_LAUNCHER" variable and corresponding "TEST_LAUNCHER"
target property were added to specify a launcher to be used by
executable targets when invoked by tests added by the "add_test()"
command.
Properties
--
* The "CROSSCOMPILING_EMULATOR" ta
Re: GSoC: Interested on "Port oss-fuzz tests to QT6"
El dilluns, 4 de març de 2024, a les 7:42:53 (CET), Khalid Masum va escriure: > Dear Albert Astals Cid, Hello > I am Khalid Masum, interested in doing Google Summer of Code with KDE. > The project idea: "Port oss-fuzz tests to QT6" is interesting to me and I > believe I will be able to do it next summer. > > About my knowledge prerequisite: have worked with build tools like Make, > CMake, Libtool, Autoconf, Autoconf etc before and I am positive I have > the necessary knowledge. > > It would be great if you could help me get started with this. Looking > forward to hearing from you. Have you read this? https://community.kde.org/GSoC What do you mean exactly with "help me get started with this"? Cheers, Albert P.S: Don't start an email with "Dear Albert Astals Cid" and then send it to a mailing list that has hundreds of people in it :) > > Best regards, > Khalid Masum
Re: Kile release status
Hi Jonathan, you can find more details at https://invent.kde.org/office/kile/-/issues/13 Summary: - Kile has a couple of open crash bugs, that should be fixed first. - There exists a Qt 6/KF 6 branch. - We wanted to have a Qt-5-based release first. Not sure what Michel has in mind, he currently is kind of the maintainer. Helping testing Kile and addressing the crash bugs would definitely be helpful. Bye Christoph Am 04.03.24 um 17:28 schrieb Jonathan Riddell: Following the release of Qt 6 based libraries and apps users of Kile are reporting that it no longer runs for them. There does not seem to have been a stable release of Kile in many years and even the unstable beta is 2 years old but the app does seem to get development and have Qt 6 code ready to go (although when I tried to compile it against Frameworks 6.0 it had various include errors). What are the chances of getting a Kile release in the near future? Jonathan
Kile release status
Following the release of Qt 6 based libraries and apps users of Kile are reporting that it no longer runs for them. There does not seem to have been a stable release of Kile in many years and even the unstable beta is 2 years old but the app does seem to get development and have Qt 6 code ready to go (although when I tried to compile it against Frameworks 6.0 it had various include errors). What are the chances of getting a Kile release in the near future? Jonathan
GSoC: Interested on "Port oss-fuzz tests to QT6"
Dear Albert Astals Cid, I am Khalid Masum, interested in doing Google Summer of Code with KDE. The project idea: "Port oss-fuzz tests to QT6" is interesting to me and I believe I will be able to do it next summer. About my knowledge prerequisite: have worked with build tools like Make, CMake, Libtool, Autoconf, Autoconf etc before and I am positive I have the necessary knowledge. It would be great if you could help me get started with this. Looking forward to hearing from you. Best regards, Khalid Masum
