Re: [CMake] transitive linkage of OBJECT library targets
This is a known limitation of the current design. Only directly linked object library objects are propagated. For more details on why see: https://gitlab.kitware.com/cmake/cmake/issues/18090 On Wed, May 22, 2019 at 1:48 AM Richard Szabo wrote: > > Hi cmakers > > I'm trying to get the following example working: > ``` > cmake_minimum_required(VERSION 3.14) > project(test_object_lib_nesting) > > set(CMAKE_CXX_STANDARD 14) > > add_library(first_object_lib OBJECT first.cpp) > > add_library(second_object_lib OBJECT second.cpp) > > target_link_libraries(second_object_lib first_object_lib) > > add_executable(test_object_lib_nesting main.cpp) > > target_link_libraries(test_object_lib_nesting second_object_lib) > ``` > > The problem I have that the linker command line will have only the > second.cpp.o for linking the first.cpp.o will not be added as link > object to the exe. Causing missing symbols on exe linkage. > > How to transitively resolve and link "nested" Object library targets ?. > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio platform name ("Win32", "x64") back on CMake GUI window?
Can you submit this to our issue tracker please ( https://gitlab.kitware.com/cmake/cmake/issues ) On Wed, May 22, 2019 at 9:44 AM Niels Dekker wrote: > > Previous versions of CMake GUI (prior to CMake 3.14) always displayed > the name of the selected platform (typically "Win32" or "Win64") with > the current generator, for example: > >"Current Generator: Visual Studio 14 2015 Win64" > > It was very convenient to have the platform name displayed on the main > window of the CMake GUI. > > When a new Visual Studio project is generated "from scratch" by CMake > 3.14, the platform name is no longer displayed with the Current > Generator. As I just tested with CMake 3.14.4, generating for VS2017 > x64. > > Would it be possible to get the VS platform name back onto the CMake GUI > main window? > > > Kind regards, Niels > -- > Niels Dekker > Scientific programmer > LKEB, Leiden University Medical Center > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Specifying VS 2019 LLVM toolset on CMake command line?
I believe it is "-T llvm" when using the Visual Studio Generators On Sun, May 19, 2019 at 3:33 PM Osman Zakir wrote: > > How do I specify the VS 2019 LLVM toolset when configuring a build with CMake > on the command line? > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Support of compile features for Fujitsu C++ Compiler
I believe the only way is to have your version of Fujitsu-DetermineCompiler.cmake be installed over the one provided by CMake. When it comes to known compilers CMake explicitly includes the version it ships. On Tue, May 7, 2019 at 11:01 PM Zehner Paul wrote: > > Robert, > > Thank you for the advice. > > As I want to take account of compiler version, I overrided the > `Fujitsu-DetermineCompiler.cmake` file by copy-pasting and editing it in the > folder of `CMAKE_MODULE_PATH`. However, the installation > `Fujitsu-DetermineCompiler.cmake` file is always used instead. What should I > do? > > Best regards, > > -- > > Paul Zehner, Ph. D. > > Invited Researcher > > Numerical Simulation Research Unit > > Japan Aerospace Exploration Agency > > 7-44-1 Jindaiji Higashi-machi, Chofu-shi, Tokyo > > 182-8522, Japan > > Tel. +81-50-3362-7933 > > Fax. +81-422-40-3327 > > zehner.p...@jaxa.jp > > www.jaxa.jp > > > From: Robert Maynard > Sent: Friday, April 26, 2019 23:32 > To: Zehner Paul > Cc: Kai Wolf; cmake@cmake.org > Subject: Re: [CMake] Support of compile features for Fujitsu C++ Compiler > > For an initial implementation I would base the work on the PGI > compiler module ( > https://gitlab.kitware.com/cmake/cmake/blob/v3.14.3/Modules/Compiler/PGI-CXX.cmake > ) not the GNU-CXX module. > This will allow you to add a new compiler with only meta-language > flags ( cxx_std_11, cxx_std_14, ... ) and you avoid the complexity of > having to manually build the feature tables. > > On Fri, Apr 26, 2019 at 3:58 AM Zehner Paul wrote: > > > > Kai, > > > > > > Thanks for your answer and for your presentation. So, I will try to add > > support for this Fujitsu compiler. Is there a list of the common compile > > features that I can base me upon? I plan use `GNU-CXX.cmake` as a source of > > inspiration. > > > > > > If I succeed to complete the `Fujitsu-CXX.cmake` file, I will propose it as > > a merge request. > > > > > > -- > > > > Paul Zehner, Ph. D. > > > > Invited Researcher > > > > Numerical Simulation Research Unit > > > > Japan Aerospace Exploration Agency > > > > 7-44-1 Jindaiji Higashi-machi, Chofu-shi, Tokyo > > > > 182-8522, Japan > > > > Tel. +81-50-3362-7933 > > > > Fax. +81-422-40-3327 > > > > zehner.p...@jaxa.jp > > > > www.jaxa.jp > > > > > > > > > > From: Kai Wolf > > Sent: Friday, April 26, 2019 16:22 > > To: Zehner Paul > > Cc: cmake@cmake.org > > Subject: Re: [CMake] Support of compile features for Fujitsu C++ Compiler > > > > If you want to add support to your specific compiler, you could add or > > extend another Fujitsu-DetermineCompiler.cmake > > file and append your CMAKE_MODULE_PATH in order to CMake to find it. You > > probably also need to adjust > > *Fujitsu-CXX.cmake, Fujitsu-CXX-FeatureTests.cmake and so on. > > > > I gave a talk a few years ago that shortly explains the whole process of > > CMake initialization and compiler verification which > > you can find here: > > https://github.com/NewProggie/Talks/blob/master/2017-06-dep-management-with-cmake-MUC%2B%2B.pdf > > > > > > Greetings, > > > > Kai > > > > http://kai-wolf.me > > http://effective-cmake.com > > > > Am 26.04.2019 um 07:35 schrieb Zehner Paul : > > > > Hello Cmake community, > > > > I would like to use Cmake to build research simulation programs in a > > Fujitsu supercomputer environment. Unfortunately, it seems that Cmake > > (version 3.14) does not support any compile feature for the Fujitsu C++ > > compiler (FCCpx, version 2.0.0 P-id: T01815-02 (Jul 12 2018 13:13:18)). I > > add I am pretty new to Cmake. Searching for similar issues, I found only > > this > > [thread](https://cmake.org/pipermail/cmake-developers/2014-August/010989.html), > > which talk about basic support of the compiler. > > > > I tested it on a simple project, and the line: > > > > ```cmake > > target_compile_features(test PUBLIC cxx_std_11) > > ``` > > > > fails with this message: > > > > ``` > > CMake Error at CMakeLists.txt:15 (target_compile_features): > > target_compile_features no known features for CXX compiler > > > > "Fujitsu" > > > > version . > > > > ``` > > > > So, it seems that the compiler is detected (without its version), but >
Re: [CMake] Building CMake with custom OpenSSL
I don't believe that we test CMake with that configuration of OpenSSL. If it works, I cant promise it will continue to work going forward. On Mon, May 20, 2019 at 4:44 PM A.Dmitrovsky wrote: > > Hi, > > I am building CMake (on x64 linux) with custom OpenSSL and wondering if there > are any CMake requirements on how OpenSSL should be compiled. Specifically, > I'm interested to know if it is valid to link CMake with single-threaded > OpenSSL library (configured with "no-threads" option). > > May be it is documented somewhere? > > Regards, > Anton > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] c++2a
CMake hasn't been updated to be aware that XCode 10 added support for C++20 (via -std=c++2a). I have opened a MR to correct this which you can track at: https://gitlab.kitware.com/cmake/cmake/merge_requests/3294 On Tue, May 7, 2019 at 12:24 PM Angel Campoverde wrote: > > Hi, > > No, It does not work, I told Cmake to use c++ 20, but it still goes back to > c++17. You can see what I get here: > > https://pastebin.com/5ub18cMU > > my CMakeLists.txt is here: > > https://pastebin.com/3bwMKrWB > > do you know what could be the problem? > > Cheers. > > On Tue, May 7, 2019 at 2:33 AM Mateusz Loskot wrote: >> >> On Tue, 7 May 2019 at 01:15, Angel Campoverde >> wrote: >> > >> > I am looking at: >> > >> > https://cmake.org/cmake/help/v3.14/prop_tgt/CXX_STANDARD.html >> > >> > and I see that I can pass 20, for c++20. However I do not have that in my >> > compiler, >> > I only have c++2a and gnu++2a, this means that CMake goes back to c++17 >> >> No, it doesn't mean that. >> >> The valid values documented for CXX_STANDARD are CMake generalisation >> and not what is directly passed via -std= or /std: or whatever option >> your compiler uses. >> >> If you run this cmake command >> cmake -DCMAKE_CXX_STANDARD=20 -DCMAKE_CXX_EXTENSIONS=OFF .. >> and then >> VERBOSE=1 make >> you will clearly see that CMake generated the compiler >> command lines with -std=c++2a >> >> IFF, you are using version of GCC or clang that supports c++2a, obviously >> (i.e. GCC 8/clang 6 or later. I'm not entirely confident about clang) >> >> Best regards, >> -- >> Mateusz Loskot, http://mateusz.loskot.net >> -- >> >> Powered by www.kitware.com >> >> Please keep messages on-topic and check the CMake FAQ at: >> http://www.cmake.org/Wiki/CMake_FAQ >> >> Kitware offers various services to support the CMake community. For more >> information on each offering, please visit: >> >> CMake Support: http://cmake.org/cmake/help/support.html >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Follow this link to subscribe/unsubscribe: >> https://cmake.org/mailman/listinfo/cmake > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Support of compile features for Fujitsu C++ Compiler
For an initial implementation I would base the work on the PGI
compiler module (
https://gitlab.kitware.com/cmake/cmake/blob/v3.14.3/Modules/Compiler/PGI-CXX.cmake
) not the GNU-CXX module.
This will allow you to add a new compiler with only meta-language
flags ( cxx_std_11, cxx_std_14, ... ) and you avoid the complexity of
having to manually build the feature tables.
On Fri, Apr 26, 2019 at 3:58 AM Zehner Paul wrote:
>
> Kai,
>
>
> Thanks for your answer and for your presentation. So, I will try to add
> support for this Fujitsu compiler. Is there a list of the common compile
> features that I can base me upon? I plan use `GNU-CXX.cmake` as a source of
> inspiration.
>
>
> If I succeed to complete the `Fujitsu-CXX.cmake` file, I will propose it as a
> merge request.
>
>
> --
>
> Paul Zehner, Ph. D.
>
> Invited Researcher
>
> Numerical Simulation Research Unit
>
> Japan Aerospace Exploration Agency
>
> 7-44-1 Jindaiji Higashi-machi, Chofu-shi, Tokyo
>
> 182-8522, Japan
>
> Tel. +81-50-3362-7933
>
> Fax. +81-422-40-3327
>
> zehner.p...@jaxa.jp
>
> www.jaxa.jp
>
>
>
>
> From: Kai Wolf
> Sent: Friday, April 26, 2019 16:22
> To: Zehner Paul
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Support of compile features for Fujitsu C++ Compiler
>
> If you want to add support to your specific compiler, you could add or extend
> another Fujitsu-DetermineCompiler.cmake
> file and append your CMAKE_MODULE_PATH in order to CMake to find it. You
> probably also need to adjust
> *Fujitsu-CXX.cmake, Fujitsu-CXX-FeatureTests.cmake and so on.
>
> I gave a talk a few years ago that shortly explains the whole process of
> CMake initialization and compiler verification which
> you can find here:
> https://github.com/NewProggie/Talks/blob/master/2017-06-dep-management-with-cmake-MUC%2B%2B.pdf
>
>
> Greetings,
>
> Kai
>
> http://kai-wolf.me
> http://effective-cmake.com
>
> Am 26.04.2019 um 07:35 schrieb Zehner Paul :
>
> Hello Cmake community,
>
> I would like to use Cmake to build research simulation programs in a Fujitsu
> supercomputer environment. Unfortunately, it seems that Cmake (version 3.14)
> does not support any compile feature for the Fujitsu C++ compiler (FCCpx,
> version 2.0.0 P-id: T01815-02 (Jul 12 2018 13:13:18)). I add I am pretty new
> to Cmake. Searching for similar issues, I found only this
> [thread](https://cmake.org/pipermail/cmake-developers/2014-August/010989.html),
> which talk about basic support of the compiler.
>
> I tested it on a simple project, and the line:
>
> ```cmake
> target_compile_features(test PUBLIC cxx_std_11)
> ```
>
> fails with this message:
>
> ```
> CMake Error at CMakeLists.txt:15 (target_compile_features):
> target_compile_features no known features for CXX compiler
>
> "Fujitsu"
>
> version .
>
> ```
>
> So, it seems that the compiler is detected (without its version), but compile
> features are not known. To be sure, I ran this simple test to list any
> supported features:
>
> ```cmake
> cmake_minimum_required(VERSION 3.1.0 FATAL_ERROR)
> project(foobar CXX)
> message("Your C++ compiler supports these C++ features:")
> foreach(i ${CMAKE_CXX_COMPILE_FEATURES})
> message("${i}")
> endforeach()
> ```
>
> and no feature are listed.
>
> So, what should I do from now on? Are there some people here using Cmake with
> Fujitsu who could help me? Should I propose a patch with the different
> compile features of the compiler? Or should I address it to Fujitsu?
>
> Thanks for your help,
>
> --
> Paul Zehner, Ph. D.
> Invited Researcher
> Numerical Simulation Research Unit
> Japan Aerospace Exploration Agency
> 7-44-1 Jindaiji Higashi-machi, Chofu-shi, Tokyo
> 182-8522, Japan
> Tel. +81-50-3362-7933
> Fax. +81-422-40-3327
> zehner.p...@jaxa.jp
> www.jaxa.jp
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
>
[CMake] [ANNOUNCE] CMake 3.14.3 available for download
We are pleased to announce that CMake 3.14.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.14.3 since 3.14.2: Ben Boeckel (1): FindOpenGL: look for GLVND libraries with a libglvnd suffix Brad King (4): FindBoost: Add support for MSVC toolset version 14.2 IRSL: Update redist directory for VS 2019 update 1 VS: Provide the default platform name to project code CMake 3.14.3 Christian Pfeiffer (1): FindQt3: Restore missing lib and bin path suffixes Rolf Eike Beer (1): FindBoost: Fix detection with version suffixes on Gentoo -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake 3.15.3 available for download
We are pleased to announce that CMake 3.15.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.3 since 3.15.2: Brad King (13): Flang: Implement MSVC runtime library abstraction CTest: Fix --show-only=json-v1 output with REQUIRED_FILES property cmGlobalGenerator: Fix CheckCompilerIdCompatibility local var lifetime cmAffinity: Add include for CPU_ZERO on Alpine Linux find_path: Fix crash on empty old-style list of names fileapi: Fix codemodel v2 target file name for CMP0037 OLD behavior FindBoost: Simplify conditional block for last known version FindBoost: Remove incorrect 1.70 timer dependency FindBoost: Unwrap compatibility INTERFACE targets for legacy variables FindBoost: Add support for Boost 1.71 FindBoost: Clarify role of legacy variables in warning message FindBoost: Tolerate future Boost INTERFACE libraries CMake 3.15.3 Chuck Atkins (1): CrayPrgEnv: Change default linking mode based on PE version M Furkan USLU (1): ccmake: handle cache entries with empty STRINGS property Marvin Schmidt (1): libarchive: We now require at least version 3.3.3 Robert Maynard (1): FindMPI: Restore MPI__COMPILE_FLAGS and MPI__COMPILE_OPTIONS Sebastian Holtermann (3): Ninja: Add support for ADDITIONAL_CLEAN_FILES in custom targets Tests: Extend MakeClean test to test various target types Autogen: Fix AUTOUIC segfault, when file includes colliding ui_*.h file -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake 3.15.4 available for download
We are pleased to announce that CMake 3.15.4 is now available for download. This release fixes a regression in EXCLUDE_FROM_ALL. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.4 since 3.15.3: Brad King (10): VS: Tell VS 16.4 not to verify SYMBOLIC custom command outputs Tests: Teach RunCMake to support a custom working directory Tests: Revise RunCMake.add_subdirectory ExcludeFromAll to avoid globbing Tests: Clarify target names in RunCMake.add_subdirectory ExcludeFromAll Makefiles: Revert "Make build root targets ... recursive" Restore "all" target in subdirectories marked EXCLUDE_FROM_ALL Help: Add release note for EXCLUDE_FROM_ALL fix in 3.14.7 Help: Add release note for EXCLUDE_FROM_ALL fix in 3.15.4 Help: Mention 3.14.7 EXCLUDE_FROM_ALL fix in 3.15.4 release note CMake 3.15.4 LE GARREC Vincent (1): Help: Document VS 2019 toolset in MSVC_TOOLSET_VERSION -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake 3.14.7 available for download
We are pleased to announce that CMake 3.14.7 is now available for download. This release fixes a regression in EXCLUDE_FROM_ALL. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.14.7 since 3.14.6: Brad King (6): Tests: Teach RunCMake to support a custom working directory Tests: Revise RunCMake.add_subdirectory ExcludeFromAll to avoid globbing Tests: Clarify target names in RunCMake.add_subdirectory ExcludeFromAll Restore "all" target in subdirectories marked EXCLUDE_FROM_ALL Help: Add release note for EXCLUDE_FROM_ALL fix in 3.14.7 CMake 3.14.7 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake Discourse forum now available
A Discourse forum is now available for the CMake community: https://discourse.cmake.org Discourse offers users more control over their level of participation, allowing them to subscribe or unsubscribe by category or individual topic. Users may choose to participate by web forum, email, or both. To get started, see our Forum Help page: https://discourse.cmake.org/faq User accounts may be created using Email Registration, a GitHub Account, or a Google Account. For those who prefer email over web forums, the Forum Help page includes instructions to participate in the forum purely via email. Creating topics in the forum via email (and receiving replies) is supported *with or without* registering a user account. User accounts may be configured to receive email notifications for forum activity at several levels of granularity, or to receive email notifications for all activity like a mailing list. To facilitate a transition period, the current mailman-based mailing lists will remain active until at least the end of March 2020, and their archives will remain available after that. See you on discourse.cmake.org! -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake 3.16.0-rc3 is ready for testing
I am proud to announce the third CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more significant changes in CMake 3.16 are:
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
* The "target_precompile_headers()" command was added to specify a
list of headers to precompile for faster compilation times.
* The "UNITY_BUILD" target property was added to tell generators to
batch include source files for faster compilation times.
* The "find_file()", "find_library()", "find_path()",
"find_package()", and "find_program()" commands have learned to
check the following variables to control searching
* "CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH" - Controls the searching
the cmake-specific environment variables.
* "CMAKE_FIND_USE_CMAKE_PATH" - Controls the searching the cmake-
specific cache variables.
* "CMAKE_FIND_USE_CMAKE_SYSTEM_PATH" - Controls the searching
cmake platform specific variables.
* "CMAKE_FIND_USE_PACKAGE_ROOT_PATH" - Controls the searching of
"_ROOT" variables.
* "CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH" - Controls the
searching the standard system environment variables.
* The "file()" command learned a new sub-command,
"GET_RUNTIME_DEPENDENCIES", which allows you to recursively get the
list of libraries linked by an executable or library. This sub-
command is intended as a replacement for "GetPrerequisites".
* "ctest(1)" now has the ability to serialize tests based on
hardware requirements for each test. See Hardware Allocation for
details.
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One may manually enable runtime linking for shared libraries
and/or loadable modules by adding "-Wl,-G" to their link flags (e.g.
in the "CMAKE_SHARED_LINKER_FLAGS" or "CMAKE_MODULE_LINKER_FLAGS"
variable). One may manually enable runtime linking for executables
by adding "-Wl,-brtl" to their link flags (e.g. in the
"CMAKE_EXE_LINKER_FLAGS" variable).
* "cmake(1)" "-E" now supports "true" and "false" commands, which do
nothing while returning exit codes of 0 and 1, respectively.
* "cmake(1)" gained a "--trace-redirect=" command line option
that can be used to redirect "--trace" output to a file instead of
"stderr".
* The "cmake(1)" "--loglevel" command line option has been renamed
to "--log-level" to make it consistent with the naming of other
command line options. The "--loglevel" option is still supported to
preserve backward compatibility.
* The "CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY" variable has been
deprecated. Use the "CMAKE_FIND_USE_PACKAGE_REGISTRY" variable
instead.
* The "GetPrerequisites" module has been deprecated, as it has been
superceded by "file(GET_RUNTIME_DEPENDENCIES)".
CMake 3.16 Release Notes
Changes made since CMake 3.15 include the following.
New Features
Languages
-
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
Compilers
-
* The "Clang" compiler is now supported on "Solaris".
Platforms
-
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One
[CMake] [ANNOUNCE] CMake 3.15.5 available for download
We are pleased to announce that CMake 3.15.5 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.5 since 3.15.4: Alan W. Irwin (1): Help: Fix COMPILE_LANG_AND_ID genex example Brad King (7): VS: Fix support for v142 toolset minor versions Xcode: Restore CMAKE_XCODE_GENERATE_SCHEME for custom targets VS: Tell VS 16.4 not to verify CMake-provided custom command outputs VS: Add toolset v142 CSharp flag table IRSL: Prefer MSVC runtime libraries from newest toolset first IRSL: Install vcruntime140_1.dll if available CMake 3.15.5 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake 3.15.6 available for download
We are pleased to announce that CMake 3.15.6 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.6 since 3.15.5: Alexander Grund (1): Check for support before adding bigtoc linker flag Ben Boeckel (1): FindPostgreSQL: support version encoding used in pre-10 releases Brad King (4): CMakeParseImplicitIncludeInfo: Remove all CR chars from compiler output VS: Fix support for v142 toolset minor versions in VS 16.5+ FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX CMake 3.15.6 Deniz Bahadir (1): FindBoost: Prevent warning due to new meta-component "ALL" of Boost 1.73 Markus Mittendrein (1): FindGTK2: Add harfbuzz to GTK2_INCLUDE_DIRS -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] ANNOUNCE] CMake 3.16.1 available for download
We are pleased to announce that CMake 3.16.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.16.1 since 3.16.0: Alexander Grund (2): bootstrap: Add target_link_options command Check for support before adding bigtoc linker flag Ben Boeckel (1): TestDriver: ignore strcpy call Brad King (2): FindThreads: Restore hard-coded '-l' flag on library name CMake 3.16.1 Cristian Adam (5): PCH: Do not add #pragma system_header for Xcode generator Unity/PCH: Skip more target types when adding automatic sources Unity: Generic source file handling for all generators Unity: Proper handling of object libraries PCH: Use the target's PREFIX for building the pdb file name Kyle Edwards (1): CTest Resource Allocation: Add test for spec file with no version Tobias Taschner (1): FindwxWidgets: Add support for 3.1.3 on macOS -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.16.0-rc2 is ready for testing
I am proud to announce the second CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more significant changes in CMake 3.16 are:
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
* The "target_precompile_headers()" command was added to specify a
list of headers to precompile for faster compilation times.
* The "UNITY_BUILD" target property was added to tell generators to
batch include source files for faster compilation times.
* The "find_file()", "find_library()", "find_path()",
"find_package()", and "find_program()" commands have learned to
check the following variables to control searching
* "CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH" - Controls the searching
the cmake-specific environment variables.
* "CMAKE_FIND_USE_CMAKE_PATH" - Controls the searching the cmake-
specific cache variables.
* "CMAKE_FIND_USE_CMAKE_SYSTEM_PATH" - Controls the searching
cmake platform specific variables.
* "CMAKE_FIND_USE_PACKAGE_ROOT_PATH" - Controls the searching of
"_ROOT" variables.
* "CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH" - Controls the
searching the standard system environment variables.
* The "file()" command learned a new sub-command,
"GET_RUNTIME_DEPENDENCIES", which allows you to recursively get the
list of libraries linked by an executable or library. This sub-
command is intended as a replacement for "GetPrerequisites".
* "ctest(1)" now has the ability to serialize tests based on
hardware requirements for each test. See Hardware Allocation for
details.
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One may manually enable runtime linking for shared libraries
and/or loadable modules by adding "-Wl,-G" to their link flags (e.g.
in the "CMAKE_SHARED_LINKER_FLAGS" or "CMAKE_MODULE_LINKER_FLAGS"
variable). One may manually enable runtime linking for executables
by adding "-Wl,-brtl" to their link flags (e.g. in the
"CMAKE_EXE_LINKER_FLAGS" variable).
* "cmake(1)" "-E" now supports "true" and "false" commands, which do
nothing while returning exit codes of 0 and 1, respectively.
* "cmake(1)" gained a "--trace-redirect=" command line option
that can be used to redirect "--trace" output to a file instead of
"stderr".
* The "cmake(1)" "--loglevel" command line option has been renamed
to "--log-level" to make it consistent with the naming of other
command line options. The "--loglevel" option is still supported to
preserve backward compatibility.
* The "CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY" variable has been
deprecated. Use the "CMAKE_FIND_USE_PACKAGE_REGISTRY" variable
instead.
* The "GetPrerequisites" module has been deprecated, as it has been
superceded by "file(GET_RUNTIME_DEPENDENCIES)".
CMake 3.16 Release Notes
Changes made since CMake 3.15 include the following.
New Features
Languages
-
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
Compilers
-
* The "Clang" compiler is now supported on "Solaris".
Platforms
-
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One
Re: [CMake] Custom installation of cmake
The easiest way is to specify the custom compiler via the CC and CXX environment variables. On Sat, Oct 19, 2019 at 2:19 PM Mahmood Naderan via CMake wrote: > > OK and how about custom installation path of cmake? > > > Regards, > Mahmood > > > On Saturday, October 19, 2019, 4:44:28 PM GMT+3:30, 15 knots > wrote: > > > What worked for me, is to add 'ools/gcc-7.1.0/bin/' in front of the > PATh environment variable for the time cmake is invoked. E.g from > bash. > PATH=tools/gcc-7.1.0/bin/;$PATH cmake -G ... > > Martin > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake 3.16.0-rc4 is ready for testing
ted by GTest 1.8.1. * The "project()" command no longer strips leading zeros in version components. See policy "CMP0096". * The Qt Compressed Help file is now named "CMake.qch", which no longer contains the release version in the file name. When CMake is upgraded in-place, the name and location of this file will remain constant. Tools such as IDEs, help viewers, etc. should now be able to refer to this file at a fixed location that remains valid across CMake upgrades. * "RPATH" entries are properly escaped in the generated CMake scripts used for installation. See policy "CMP0095". * When using "CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS" on Windows the auto- generated exports are now updated only when the object files providing the symbols are updated. Changes made since CMake 3.16.0-rc3: Alex Turbov (1): CPack: Remove CPACK_INSTALL_CMAKE_CONFIGURATIONS Arkadiusz Drabczyk (1): Tutorial: replace Unicode EN DASH with ASCII dash Ben Boeckel (3): Help: drop confusing reference to `if()` from `$` FindPostgreSQL: support version encoding used in pre-10 releases FindPostgreSQL: also search for libraries in the MacPorts suffix Brad King (20): CTest: Rename PROCESSES test property to RESOURCE_GROUPS CTest: Rename "Processes" lexer to "ResourceGroups" Help/dev: Update maintainer guide for Discourse transition cmGlobalXCodeGenerator: Mark known source locations Xcode: Fix generated references to CMakeLists.txt files CMakeCPack: Update Debian package contact email Help: Replace links to mailing lists with links to our Discourse Forum README: Update links to cmake.org pages README: Replace link to mailing list the CMake Discourse Forum CMakeSystemSpecificInformation: Replace mailing list with Discourse Forum FindBinUtils: Revert "Use the compiler to get the path to compiler tools" Help: Document target_precompile_headers genex with angle brackets CTestCoverageCollectGCOV: Fix typo in ctest_coverage_collect_gcov docs expat: Update script to get Expat 2.2.9 expat: Update CMake build for 2.2.9 Tests: Fix ExportImport PCH expectation on Cray Classic compiler Tests: Add RunCMake.CPackCommandLine case for multi-config package Tests: Organize Objective C/C++ test directories CPack: Restore support for custom package configuration templates CMake 3.16.0-rc4 Charles Barto (1): Help: Clarify load_cache documentation of first parameter Craig Scott (14): ForceToRelativePath: Fix spurious assertion when local path is root dir Help: list(REMOVE_ITEM) removes all instances, not just the first found Help: Typo and grammar fixes for file(GET_RUNTIME_DEPENDENCIES) Tutorial: clean up typos, grammar and formatting RPATH: Remove stray indent in generated file(RPATH_CHANGE) command Help: Fix inaccuracies in INSTALL_REMOVE_ENVIRONMENT_RPATH docs CTest: Rename hardware -> resources for CMake variables, command options cmCTestMultiProcessHandler: Rename resource locking functions CTest: Rename hardware -> resources for source code CTest: Rename hardware -> resources for RunCMake tests Help: Improve readability and fix inaccuracies in unity build docs Help: Reorganise target_precompile_headers() docs for readability Help: Provide guidance on INTERFACE for target_precompile_headers() Help: Clarify compile features handling for OBJC and OBJCXX Craig Sturdy (1): FindwxWidgets: Add support for wxQt Cristian Adam (13): PCH: Add support for OBJC/OBJCXX languages CMakeVersion.rc: Fix build with llvm-rc ObjC: Mark explicitly the language for compilation Unity build: Include GENERATED files into unity build ObjC: Set same settings for all languages supported on Darwin ObjC: Add try_compile support PCH: No repeated path for internal generated PCH files Unity: Don't include sources with HEADER_FILE_ONLY property set ObjC: Document ObjC/ObjCXX standard properties / variables ObjC: Add OBJC/OBJCXX flags to Xcode projects ObjC: Initialize ObjC/XX standard properties from C/C++ counterparts ObjC: Proper initialization of ObjC/XX standard properties PCH: Do not issue an error on duplicate target_precompile_headers call Daniel Eiband (2): cmFileAPI: Resolve full path in PCH source comparison UnityBuild: Resolve full paths of unity source includes Deniz Bahadir (1): FindBoost: Prevent warning due to new meta-component "ALL" of Boost 1.73 Expat Upstream (1): expat 2019-09-25 (a7bc26b6) Grant Kim (1): FindwxWidgets: Add link dependencies for MinGW Kyle Edwards (2): Help: Fix error in resource allocation example Tests: Fix reliance on undefined behavior of cm::optional Marc Aldorasi (2): Help: Reference IMPORTED_IMPLIB from the IMPORTED_LOCATION documentation Help: Both add_custom_command signatures support COMMAND_EXPAND_LISTS Mateusz Janek (1): source_group: ensure that passed file is not a directory Robert Maynard (3): Help: Remove out of date bounds on compile feature supported versions find_package: Add support for CMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY Help: Clarify what 'aware' means as it relates to C++ standards Saleem Abdulrasool (3): Swift: Allow build and installed RPATHs to differ Swift: support `INSTALL_NAME_DIR` on Darwin Swift: support `-rpath` on Darwin Tomasz Słodkowicz (1): FindwxWidgets: Add support for 3.1.3 VS binaries -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.16.0 available for download
I am happy to announce that CMake 3.16.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more significant changes in CMake 3.16 are:
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
* The "target_precompile_headers()" command was added to specify a
list of headers to precompile for faster compilation times.
* The "UNITY_BUILD" target property was added to tell generators to
batch include source files for faster compilation times.
* The "find_file()", "find_library()", "find_path()",
"find_package()", and "find_program()" commands have learned to
check the following variables to control searching
* "CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH" - Controls the searching
the cmake-specific environment variables.
* "CMAKE_FIND_USE_CMAKE_PATH" - Controls the searching the cmake-
specific cache variables.
* "CMAKE_FIND_USE_CMAKE_SYSTEM_PATH" - Controls the searching
cmake platform specific variables.
* "CMAKE_FIND_USE_PACKAGE_ROOT_PATH" - Controls the searching of
"_ROOT" variables.
* "CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH" - Controls the
searching the standard system environment variables.
* The "file()" command learned a new sub-command,
"GET_RUNTIME_DEPENDENCIES", which allows you to recursively get the
list of libraries linked by an executable or library. This sub-
command is intended as a replacement for "GetPrerequisites".
* "ctest(1)" now has the ability to serialize tests based on
resource requirements for each test. See Resource Allocation for
details.
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One may manually enable runtime linking for shared libraries
and/or loadable modules by adding "-Wl,-G" to their link flags (e.g.
in the "CMAKE_SHARED_LINKER_FLAGS" or "CMAKE_MODULE_LINKER_FLAGS"
variable). One may manually enable runtime linking for executables
by adding "-Wl,-brtl" to their link flags (e.g. in the
"CMAKE_EXE_LINKER_FLAGS" variable).
* "cmake(1)" "-E" now supports "true" and "false" commands, which do
nothing while returning exit codes of 0 and 1, respectively.
* "cmake(1)" gained a "--trace-redirect=" command line option
that can be used to redirect "--trace" output to a file instead of
"stderr".
* The "cmake(1)" "--loglevel" command line option has been renamed
to "--log-level" to make it consistent with the naming of other
command line options. The "--loglevel" option is still supported to
preserve backward compatibility.
* The "CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY" variable has been
deprecated. Use the "CMAKE_FIND_USE_PACKAGE_REGISTRY" variable
instead.
* The "GetPrerequisites" module has been deprecated, as it has been
superceded by "file(GET_RUNTIME_DEPENDENCIES)".
CMake 3.16 Release Notes
Changes made since CMake 3.15 include the following.
New Features
Languages
-
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
Compilers
-
* The "Clang" compiler is now supported on "Solaris".
Platforms
-
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
Re: [CMake] Link options not transitive
You should report this on the CMake issue tracker: https://gitlab.kitware.com/cmake/cmake/issues/ On Sat, Nov 23, 2019 at 12:03 PM Martin Krošlák wrote: > > Hi, > > I have recently encountered what I believe might be a bug, where > INTERFACE_LINK_OPTIONS are not carried over static libraries. > Following is the simplest CMakeLists.txt that demonstrates the > problem: > > cmake_minimum_required(VERSION 3.16) > project(LinkOptionsNotTransitive) > add_library(A SHARED A.cpp) > add_library(B STATIC B.cpp) > add_executable(C C.cpp) > target_link_options(A INTERFACE "/DELAYLOAD:A.dll") > target_link_libraries(B PRIVATE A) > target_link_libraries(C PRIVATE B) > > I tested this with Visual Studio 2017 generator and both cmake 3.15.4 > and 3.16.0-rc4, with the same result. > > When inspecting generated solution, C is linking both A.lib and B.lib > (as it should), but /DELAYLOAD flag is not applied to it. If B has > PUBLIC dependency on A, then /DELAYLOAD flag is also correctly carried > over. I get the impression that target_link_options behaves as eg. > target_include_directories, which are not carried over PRIVATE > dependencies. Given that these are linker options, I would expect them > to follow same rules as target_link_libraries, which will carry over > until nearest linker invocation. Is there any reason for this > inconsistency, or is it just a bug and if so, what would be the best > way to report it? > > -- > Sincerely, > Martin Krošlák > -- > > Powered by kitware.com/cmake > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit https://cmake.org/services > > Visit other Kitware open-source projects at https://www.kitware.com/platforms > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > > This mailing list is deprecated in favor of https://discourse.cmake.org -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing
I am proud to announce the first CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more significant changes in CMake 3.16 are:
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
* The "target_precompile_headers()" command was added to specify a
list of headers to precompile for faster compilation times.
* The "UNITY_BUILD" target property was added to tell generators to
batch include source files for faster compilation times.
* The "find_file()", "find_library()", "find_path()",
"find_package()", and "find_program()" commands have learned to
check the following variables to control searching
* "CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH" - Controls the searching
the cmake-specific environment variables.
* "CMAKE_FIND_USE_CMAKE_PATH" - Controls the searching the cmake-
specific cache variables.
* "CMAKE_FIND_USE_CMAKE_SYSTEM_PATH" - Controls the searching
cmake platform specific variables.
* "CMAKE_FIND_USE_PACKAGE_ROOT_PATH" - Controls the searching of
"_ROOT" variables.
* "CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH" - Controls the
searching the standard system environment variables.
* The "file()" command learned a new sub-command,
"GET_RUNTIME_DEPENDENCIES", which allows you to recursively get the
list of libraries linked by an executable or library. This sub-
command is intended as a replacement for "GetPrerequisites".
* "ctest(1)" now has the ability to serialize tests based on
hardware requirements for each test. See Hardware Allocation for
details.
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One may manually enable runtime linking for shared libraries
and/or loadable modules by adding "-Wl,-G" to their link flags (e.g.
in the "CMAKE_SHARED_LINKER_FLAGS" or "CMAKE_MODULE_LINKER_FLAGS"
variable). One may manually enable runtime linking for executables
by adding "-Wl,-brtl" to their link flags (e.g. in the
"CMAKE_EXE_LINKER_FLAGS" variable).
* "cmake(1)" "-E" now supports "true" and "false" commands, which do
nothing while returning exit codes of 0 and 1, respectively.
* "cmake(1)" gained a "--trace-redirect=" command line option
that can be used to redirect "--trace" output to a file instead of
"stderr".
* The "cmake(1)" "--loglevel" command line option has been renamed
to "--log-level" to make it consistent with the naming of other
command line options. The "--loglevel" option is still supported to
preserve backward compatibility.
* The "CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY" variable has been
deprecated. Use the "CMAKE_FIND_USE_PACKAGE_REGISTRY" variable
instead.
* The "GetPrerequisites" module has been deprecated, as it has been
superceded by "file(GET_RUNTIME_DEPENDENCIES)".
CMake 3.16 Release Notes
Changes made since CMake 3.15 include the following.
New Features
Languages
-
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
Compilers
-
* The "Clang" compiler is now supported on "Solaris".
Platforms
-
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One
Re: [CMake] CMake and Ninja, RERUN_CMAKE useless?
The default generator and all other associated information ( '-D' ) is kept in the CMakeCache.txt file in the root of the build directory. The execution of `cmake -S -B ` will reload this cache before doing anything else. Have you verified that your build directory hasn't deleted this file? On Tue, Oct 8, 2019 at 8:31 PM Nagurne, James via CMake wrote: > > Hi all, > > > > My question comes from a Ninja generator build system, and is specifically > about an internal rule generated by cmake. > > What is the purpose of the RERUN_CMAKE rule generated by CMake with a Ninja > generator? > > > > In the current repo, the only reference to this rule is in > WriteTargetRebuildManifest here > > At line 1285, the rule is written out, seemingly as-is. > > > > According to lines 1274 to 1284, the only actual behavior of this command, > which is executed whenever the source CMakeLists.txt file, files included > from the CMakeLists, and some other CMake installation files change, is: > > cmake -S -B > > > > This seems completely insufficient for “re-running” cmake. The most obvious > flaw is the absence of the generator. When I’ve seen this rule fire, my Ninja > build system adds a useless Makefile to the build system, and then > (hopefully) continues building as if nothing had been done at all, without so > much as inspecting that Makefile. > > > > What about command-line arguments like -D? > > > > Am I missing the purpose of this rule or potentially doing something > non-standard? The reason I send an email is because this behavior is sending > my project into a cmake loop where it detects build.ninja is out of date, > re-runs cmake to generate a Makefile instead of a ninja build system, and > then infinitely repeats because it never actually re-ran anything. > > > > Thanks, > > JB > > Code Generation > > Texas Instruments > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] [EXTERNAL] Re: CMake and Ninja, RERUN_CMAKE useless?
If you want to do a clean rebuild you can do the following: ninja clean or cmake --build --target clean ninja or cmake --build -j N On Wed, Oct 9, 2019 at 12:00 PM Nagurne, James wrote: > > That's the piece of the puzzle I was missing. Thank you! > > Yes, I had deleted the cache because I thought that would force a complete > regeneration. I'm using a rather complicated system of ExternalProjects > (LLVM), so I figured it was the quickest way to essentially force cmake to > start from the beginning and reload those cache files without invalidating > and forcing a rebuild of the executables and libraries I had already built > > Is there a way to do what I was looking for? I wouldn't be surprised if there > wasn't, since removing those very fundamental building blocks might as well > just be an rm -rf ./* > > JB > > -Original Message- > From: Robert Maynard [mailto:robert.mayn...@kitware.com] > Sent: Wednesday, October 9, 2019 7:16 AM > To: Nagurne, James > Cc: cmake@cmake.org > Subject: [EXTERNAL] Re: [CMake] CMake and Ninja, RERUN_CMAKE useless? > > The default generator and all other associated information ( '-D' ) is > kept in the CMakeCache.txt file in the root of the build directory. > The execution of `cmake -S -B ` will reload > this cache before doing anything else. Have you verified that your > build directory hasn't deleted this file? > > On Tue, Oct 8, 2019 at 8:31 PM Nagurne, James via CMake > wrote: > > > > Hi all, > > > > > > > > My question comes from a Ninja generator build system, and is specifically > > about an internal rule generated by cmake. > > > > What is the purpose of the RERUN_CMAKE rule generated by CMake with a Ninja > > generator? > > > > > > > > In the current repo, the only reference to this rule is in > > WriteTargetRebuildManifest here > > > > At line 1285, the rule is written out, seemingly as-is. > > > > > > > > According to lines 1274 to 1284, the only actual behavior of this command, > > which is executed whenever the source CMakeLists.txt file, files included > > from the CMakeLists, and some other CMake installation files change, is: > > > > cmake -S -B > > > > > > > > This seems completely insufficient for “re-running” cmake. The most obvious > > flaw is the absence of the generator. When I’ve seen this rule fire, my > > Ninja build system adds a useless Makefile to the build system, and then > > (hopefully) continues building as if nothing had been done at all, without > > so much as inspecting that Makefile. > > > > > > > > What about command-line arguments like -D? > > > > > > > > Am I missing the purpose of this rule or potentially doing something > > non-standard? The reason I send an email is because this behavior is > > sending my project into a cmake loop where it detects build.ninja is out of > > date, re-runs cmake to generate a Makefile instead of a ninja build system, > > and then infinitely repeats because it never actually re-ran anything. > > > > > > > > Thanks, > > > > JB > > > > Code Generation > > > > Texas Instruments > > > > -- > > > > Powered by www.kitware.com > > > > Please keep messages on-topic and check the CMake FAQ at: > > http://www.cmake.org/Wiki/CMake_FAQ > > > > Kitware offers various services to support the CMake community. For more > > information on each offering, please visit: > > > > CMake Support: http://cmake.org/cmake/help/support.html > > CMake Consulting: http://cmake.org/cmake/help/consulting.html > > CMake Training Courses: http://cmake.org/cmake/help/training.html > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Follow this link to subscribe/unsubscribe: > > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)
Hi Paul, As another reference point, I verified that -DCMAKE_UNITY_BUILD=ON works with the VTK-m ( https://gitlab.kitware.com/vtk/vtk-m ) project. I only verified using a clean CMake 3.16 build directory. On Thu, Oct 10, 2019 at 6:43 PM Paul Smith wrote: > > On Thu, 2019-10-10 at 14:57 -0400, Robert Maynard via CMake wrote: > > * The "UNITY_BUILD" target property was added to tell generators to > > batch include source files for faster compilation times. > > Are there any instructions on how to make this work? I tried this: > > cmake -G 'Unix Makefiles' -DCMAKE_UNITY_BUILD=ON . > > Then ran "make". The output showed I had just as many output .o files > as input .cpp files and that make ran one compile command per .cpp > file. > > Is there something else I need to do to enable unity builds in my cmake > files, than just give the above option? The docs imply that the above > is all that's needed. > > Cheers! > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake 3.16.2 available for download
We are pleased to announce that CMake 3.16.2 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.16.2 since 3.16.1: Brad King (6): VS: Fix support for v142 toolset minor versions in VS 16.5+ FindBLAS: Consider OpenBLAS with thread libraries only with C or CXX FindBoost: Add support for Boost 1.72 Autogen: Revert processing of .hh files for compatibility FindLAPACK: Fix support for LAPACK symbols inside BLAS libraries CMake 3.16.2 Cristian Adam (1): PCH: Append pch header file to list of forced include files Michael Dickens (1): Tests: Fix testCTestResourceSpec struct initialization for some compilers -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.17.0-rc1 is ready for testing
I am proud to announce the first CMake 3.17 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.17 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.17/release/3.17.html Some of the more significant changes in CMake 3.17 are: * "cmake(1)" gained a "Ninja Multi-Config" generator, which is similar to the "Ninja" generator but can be used to build multiple configurations at once. * Visual Studio Generators learned to support per-config sources. Previously only Command-Line Build Tool Generators supported them. * The "Compile Features" functionality now offers meta-features for the CUDA language standard levels (e.g. "cuda_std_03", "cuda_std_14"). See "CMAKE_CUDA_KNOWN_FEATURES". * The "CMAKE_CUDA_RUNTIME_LIBRARY" variable and "CUDA_RUNTIME_LIBRARY" target property were introduced to select the CUDA runtime library used when linking targets that use CUDA. * The "FindCUDAToolkit" module was added to find the CUDA Toolkit without enabling CUDA as a language. * "cmake(1)" gained a "--debug-find" command-line option to enable additional human-readable output on where find commands search. * The "CMAKE_FIND_DEBUG_MODE" variable was introduced to print extra find call information during the cmake run to standard error. Output is designed for human consumption and not for parsing. * The "FindCURL" module learned to find CURL using the "CURLConfig.cmake" package configuration file generated by CURL’s cmake buildsystem. It also gained a new "CURL_NO_CURL_CMAKE" option to disable this behavior. * The "FindPython" module has learned to find Python components in active virtual environments managed by "conda". * The "ctest(1)" tool gained a "--no-tests=<[error|ignore]>" option to explicitly set and unify the behavior between direct invocation and script mode if no tests were found. * The "ctest(1)" tool gained a "--repeat :" option to specify conditions in which to repeat tests. This generalizes the existing "--repeat-until-fail " option to add modes for "until-pass" and "after-timeout". * Target link properties "INTERFACE_LINK_OPTIONS", "INTERFACE_LINK_DIRECTORIES" and "INTERFACE_LINK_DEPENDS" are now transitive over private dependencies on static libraries. See policy "CMP0099". * When using MinGW tools, the "find_library()" command no longer finds ".dll" files by default. Instead it expects ".dll.a" import libraries to be available. * The "Ninja" generator now prefers the first ninja build tool to appear in the "PATH" no matter whether it is called "ninja-build", "ninja", or "samu". Previously the first of those names to appear anywhere in the "PATH" would be preferred. * "cmake(1)" gained a "-E rm" command-line tool that can be used to remove directories and files. This supersedes the existing "-E remove" and "-E remove_directory" tools and has better semantics. CMake 3.17 Release Notes Changes made since CMake 3.16 include the following. New Features Generators -- * "cmake(1)" gained a "Ninja Multi-Config" generator, which is similar to the "Ninja" generator but can be used to build multiple configurations at once. * Visual Studio Generators learned to support per-config sources. Previously only Command-Line Build Tool Generators supported them. * Visual Studio Generators for VS 2010 and above now support specifying the "VCTargetsPath" value for project files in "CMAKE_GENERATOR_TOOLSET" setting. * Visual Studio Generators for VS 2010 and above learned to support .NET Standard and .NET Core. See the "DOTNET_TARGET_FRAMEWORK" target property and associated "CMAKE_DOTNET_TARGET_FRAMEWORK" variable. Languages - * The "Compile Features" functionality now offers meta-features for the CUDA language standard levels (e.g. "cuda_std_03", "cuda_std_14"). See "CMAKE_CUDA_KNOWN_FEATURES". Compilers - * The IBM XL Fortran compiler is now supported by the "Ninja" generator. Command-Line * "cmake(1)" gained a "--debug-find" command-line option to enable additional human-readable output on where find commands search. * "cmake(1)" gained a "--trace-format" command-line option that can be used to set the "--trace" output format. Currently, the old human readable and the new JSON format are supported. The new JSON format is easier to parse automatically, than the existing format. * "cmake(1)" gained a "-E rm" command-line tool that can be used to remove directories and files. This supersedes the existing "-E remove" and "-E remove_directory" tools and has better semantics. Commands * The "add_custom_command()" command learned to interpret paths in "DEPENDS" arguments that are specified relative to the current binary directory. * The "foreach()" learned a new option "ZIP_LISTS" to iterate over multiple
[CMake] [ANNOUNCE] CMake 3.16.5 available for download
We are pleased to announce that CMake 3.16.5 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.16.5 since 3.16.4: Brad King (5): libarchive: Fix WideCharToMultiByte output buffer size libarchive: Add support for UTF-8 locale on Windows Propagate backtraces from LINK_LIBRARIES through to link line items Help: Update CMake 3.16 release notes for 3.16.5 CMake 3.16.5 Francisco Facioni (1): Ninja: Do not use nvcc response files with non-nvcc tools Kyle Edwards (1): install: Fix regression when using default destinations Marc Chevrier (2): FindPython: Mark non-public cache entries INTERNAL in CMake 3.16 FindPython: Do not cache computed result variables in CMake 3.16 Rolf Eike Beer (1): FindPkgConfig: set policies CMP0054 and CMP0057 to new -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.17.0-rc2 is ready for testing
IES" and "INTERFACE_LINK_DEPENDS" are now transitive over private dependencies on static libraries. See policy "CMP0099". * When using MinGW tools, the "find_library()" command no longer finds ".dll" files by default. Instead it expects ".dll.a" import libraries to be available. * The "MinGW Makefiles" generator no longer issues an error if "sh.exe" is present in the environment’s "PATH". * The "Ninja" generator now prefers the first ninja build tool to appear in the "PATH" no matter whether it is called "ninja-build", "ninja", or "samu". Previously the first of those names to appear anywhere in the "PATH" would be preferred. * With SDCC the "sdar" tool is now preferred over "sdcclib" as librarian. The latter was deprecated by SDCC 3.2.0 and removed in SDCC 3.8.6. * With SDCC the default flags no longer include any target-specific flags. Previously the default flags were hard-coded for 8051. * The "CMAKE_VS_GLOBALS" variable value now applies during compiler identification and in targets created by the "add_custom_target()" command. * The "Xcode" generator no longer hard-codes "-Wmost", "-Wno-four- char-constants", and "-Wno-unknown-pragmas" warning flags. Changes made since CMake 3.17.0-rc1: Brad King (4): Help: Replace UTF-8 apostrophe with ascii apostrophe KWSys: SystemTools: CopyFileIfDifferent: Fix endless recursion KWSys: Terminal: Add st-256color to VT100 color support whitelist CMake 3.17.0-rc2 Craig Scott (3): Tests: Fix test_clean target missing some test directories Tests: Add missing ExternalProject smoke tests ExternalProject: Quote each git --config option to handle spaces Cristian Adam (1): PCH: Copy the timestamp from an absolute header file Francisco Facioni (1): Ninja: Do not use nvcc response files with non-nvcc tools Kyle Edwards (14): Ninja Multi-Config: Fix issue with framework dependencies and Autogen Refactor: Require detail when calling cmCTestRunTest::StartFailure() CTest: Improve error reporting with bad working directory for tests Refactor: Provide more detailed error information from TryAllocateResources() CTest: Provide more detailed information on resource allocation error Tests: Fix CustComDepend test for Ninja Multi-Config Tests: Fix CFBundleTest for Ninja Multi-Config Help: Note that CMAKE_CFG_INTDIR is not fully supported on Ninja Multi-Config Help: Clarify that the CTest resource allocation feature doesn't oversubscribe Ninja Multi-Config: Remove "NMC" from variable names Generator: Don't allow Ninja Multi-Config variables on other generators Ninja Multi-Config: Always generate build.ninja foreach: Fix crash when parsing invalid integer foreach: Set fatal error on invalid range Marc Chevrier (2): FindPython: Mark non-public cache entries INTERNAL FindPython: Do not cache computed result variables Richard (1): Autogen: Recognize the new Q_NAMESPACE_EXPORT macro in AUTOMOC Robert Maynard (1): FindCUDA: Only depend on Threads::Threads on platforms that need it Rolf Eike Beer (2): FindPkgConfig: set policies CMP0054 and CMP0057 to new Tests: fix RunCMake.Make test when run on systems with non-english locale Saleem Abdulrasool (1): Swift: support `-rpath` for executables Sergey Larin (1): PCH: Clang: Update PCH usage flags to include original header -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [REMINDER] CMake transition to discourse
Reminder the CMake Discourse forum ( https://discourse.cmake.org ) is the preferred location for CMake questions and discussions. The current mailman-based mailing lists will be disabled in April 2020, and their archives will remain available after that. Reminder for those who prefer email over web forums, the Forum Help page includes instructions to participate in the forum purely via email. Creating topics in the forum via email (and receiving replies) is supported *with or without* registering a user account. -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.15.7 available for download
We are pleased to announce that CMake 3.15.7 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.15.7 since 3.15.6:
Brad King (4):
IRSL: Install msvcp140_{1,2,codecvt_ids}.dll if available
ASM_MASM: Populate MSVC runtime library abstraction table
VS: Tell VS 16.4 not to verify SYMBOLIC custom command inputs
CMake 3.15.7
Robert Maynard (1):
CUDA: Do not device link if target has no CUDA usage
--
Powered by kitware.com/cmake
Kitware offers various services to support the CMake community. For more
information on each offering, please visit https://cmake.org/services
Visit other Kitware open-source projects at https://www.kitware.com/platforms
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.16.4 available for download
We are pleased to announce that CMake 3.16.4 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.16.4 since 3.16.3: Brad King (6): ASM_MASM: Populate MSVC runtime library abstraction table VS: Tell VS 16.4 not to verify SYMBOLIC custom command inputs AIX: Restore pre-3.16 undocumented method to suppress exports with XL Android: Fix binutils selection with NDK r19+ unified toolchain VS: Do not use native unity builds on VS 2017 versions less than 15.8 CMake 3.16.4 Kyle Edwards (3): file(GET_RUNTIME_DEPENDENCIES): Tolerate empty list arguments Help: Add more variable documentation to FindMPI CPack: Fix regression in Deb description -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
Re: [CMake] [ANNOUNCE] CMake Discourse forum now available
A reminder that CMake is transitioning to Discouse, and by the end of March 2020 the mailing lists will be read-only, and the archives will remain available after that. The Discourse forum for the CMake community is: https://discourse.cmake.org Discourse offers users more control over their level of participation, allowing them to subscribe or unsubscribe by category or individual topic. Users may choose to participate by web forum, email, or both. To get started, see our Forum Help page: https://discourse.cmake.org/faq User accounts may be created using Email Registration, a GitHub Account, or a Google Account. For those who prefer email over web forums, the Forum Help page includes instructions to participate in the forum purely via email. Creating topics in the forum via email (and receiving replies) is supported *with or without* registering a user account. User accounts may be configured to receive email notifications for forum activity at several levels of granularity, or to receive email notifications for all activity like a mailing list. On Tue, Nov 5, 2019 at 12:13 PM Robert Maynard wrote: > > A Discourse forum is now available for the CMake community: > > https://discourse.cmake.org > > Discourse offers users more control over their level of participation, > allowing them to subscribe or unsubscribe by category or individual topic. > Users may choose to participate by web forum, email, or both. > > To get started, see our Forum Help page: > > https://discourse.cmake.org/faq > > User accounts may be created using Email Registration, a GitHub Account, or a > Google Account. > > For those who prefer email over web forums, the Forum Help page includes > instructions to participate in the forum purely via email. Creating topics in > the forum via email (and receiving replies) is supported *with or without* > registering a user account. User accounts may be configured to receive email > notifications for forum activity at several levels of granularity, or to > receive email notifications for all activity like a mailing list. > > To facilitate a transition period, the current mailman-based mailing lists > will remain active until at least the end of March 2020, and their archives > will remain available after that. > > See you on discourse.cmake.org! -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.16.3 available for download
We are pleased to announce that CMake 3.16.3 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.3 since 3.16.2:
Ashley Whetter (1):
FindOpenSSL: Fix ordering of dependency link flags
Brad King (3):
GNUtoMS: Add search path for VS 2019 environment scripts
IRSL: Install msvcp140_{1,2,codecvt_ids}.dll if available
CMake 3.16.3
Cristian Adam (4):
ObjC: Add _COMPILE_LAUNCHER support
ObjC: Add VISIBLITY_INLINES_HIDDEN support
Unity Build: include language in generated source file name
PCH: No repeated path for internal generated PCH files (MSVC case)
Kyle Edwards (2):
CTest: Improve error handling when reading resource spec file
CPack: Fix regression in DEB generator description
Marc Chevrier (3):
FindPython*: Fix erroneous target properties setting
macOS: Add support for new Xcode 11 frameworks directory
FindPython: ensure new Xcode framework for Python3 is detected
Miro Hrončok (1):
FindPython: Add support for version 3.9
Neil Carlson (1):
Fortran: Add support for NAG Fortran submodules
Pavel Liavonau (1):
VS: Add Fortran link flag table entries for /OPT:*
Robert Maynard (1):
CUDA: Do not device link if target has no CUDA usage
Sebastian Holtermann (1):
Autogen: Enable SKIP_UNITY_BUILD_INCLUSION on AUTORCC generated files
Silvio Traversaro (2):
FindMatlab: add R2019a and R2019b MATLAB_VERSIONS_MAPPING
FindMatlab: in matlab_add_mex use the correct version file
--
Powered by kitware.com/cmake
Kitware offers various services to support the CMake community. For more
information on each offering, please visit https://cmake.org/services
Visit other Kitware open-source projects at https://www.kitware.com/platforms
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.17.0-rc3 is ready for testing
not be fixed without breaking compatibility, and so have been superseded. Other Changes = * The "file API" index file now emits a "multiConfig" flag specifying whether or not the generator supports multiple output configurations. * Target link properties "INTERFACE_LINK_OPTIONS", "INTERFACE_LINK_DIRECTORIES" and "INTERFACE_LINK_DEPENDS" are now transitive over private dependencies on static libraries. See policy "CMP0099". * When using MinGW tools, the "find_library()" command no longer finds ".dll" files by default. Instead, it expects ".dll.a" import libraries to be available. * The "MinGW Makefiles" generator no longer issues an error if "sh.exe" is present in the environment’s "PATH". * The "Ninja" generator now prefers the first ninja build tool to appear in the "PATH" no matter whether it is called "ninja-build", "ninja", or "samu". Previously the first of those names to appear anywhere in the "PATH" would be preferred. * With SDCC the "sdar" tool is now preferred over "sdcclib" as librarian. The latter was deprecated by SDCC 3.2.0 and removed in SDCC 3.8.6. * With SDCC the default flags no longer include any target-specific flags. Previously the default flags were hard-coded for 8051. * The "CMAKE_VS_GLOBALS" variable value now applies during compiler identification and in targets created by the "add_custom_target()" command. * The "Xcode" generator no longer hard-codes "-Wmost", "-Wno-four- char-constants", and "-Wno-unknown-pragmas" warning flags. Changes made since CMake 3.17.0-rc2: Betsy McPhail (1): CTest: Fix our internal CURL_DEBUGFUNCTION to conform to CURL docs Bo Anderson (1): FindPython: Convert env CMAKE_FRAMEWORK_PATH to CMake path Brad King (5): Help: Clarify add_custom_command DEPENDS conversion to file paths Help: Fix toctree order of Xcode scheme variable and property Help: Fix 3.17 release notes for Xcode scheme settings macOS: Rename OSX_*_VERSION properties to MACHO_*_VERSION CMake 3.17.0-rc3 Craig Scott (1): Help: Cleanup minor typos and grammar in 3.17 release notes Jesse Gorzinski (1): libuv: Add support for building on IBM i (OS400) Kyle Edwards (2): Ninja Multi-Config: Don't build target dependencies for custom commands Ninja Multi-Config: Fix spurious unused variable warning Marc Chevrier (2): FindPython: python_add_library can now manage SOABI suffix. Apple Clang: add flags for C++17 standard Raul Tambre (2): cm_cxx_features: Filter out CUDA installation warnings cmAlgorithms: Fix -Wnon-c-typedef-for-linkage warnings Robert Maynard (1): CUDAToolkit: Mark find queries as advanced variables Saleem Abdulrasool (3): Swift: support Ninja Multi-Config Swift: repair RPATH handling for macOS Swift: Fix quoting of library search paths with spaces ThePrez (1): cmstd: Remove -isystem option for IBM i (OS400) Thomas Bernard (1): llvm-rc: Forward DEFINES instead of FLAGS -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake mailing list now closed
As was previously announced, CMake is stopping mailing list usage, and has transitioned to a Discourse forum (https://discourse.cmake.org). While new posts to the mailing list are disabled, all previous discussion will be archived so that the knowledge can be searched going forward. Hopefully I will see you all on discourse.cmake.org! -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake This mailing list is deprecated in favor of https://discourse.cmake.org
[CMake] [ANNOUNCE] CMake 3.17.0 available for download
I am happy to announce that CMake 3.17.0 is now available for download at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.17 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.17/release/3.17.html Some of the more significant changes in CMake 3.17 are: * "cmake(1)" gained a "Ninja Multi-Config" generator, which is similar to the "Ninja" generator but can be used to build multiple configurations at once. * Visual Studio Generators learned to support per-config sources. Previously only Command-Line Build Tool Generators supported them. * The "Compile Features" functionality now offers meta-features for the CUDA language standard levels (e.g. "cuda_std_03", "cuda_std_14"). See "CMAKE_CUDA_KNOWN_FEATURES". * The "CMAKE_CUDA_RUNTIME_LIBRARY" variable and "CUDA_RUNTIME_LIBRARY" target property were introduced to select the CUDA runtime library used when linking targets that use CUDA. * The "FindCUDAToolkit" module was added to find the CUDA Toolkit without enabling CUDA as a language. * "cmake(1)" gained a "--debug-find" command-line option to enable additional human-readable output on where "find_*" commands search. * The "CMAKE_FIND_DEBUG_MODE" variable was introduced to print extra "find_*" call information during the cmake run to standard error. Output is designed for human consumption and not for parsing. * The "FindCURL" module learned to find CURL using the "CURLConfig.cmake" package configuration file generated by CURL’s cmake buildsystem. It also gained a new "CURL_NO_CURL_CMAKE" option to disable this behavior. * The "FindPython" module has learned to find Python components in active virtual environments managed by "conda". * The "ctest(1)" tool gained a "--no-tests=<[error|ignore]>" option to explicitly set and unify the behavior between direct invocation and script mode if no tests were found. * The "ctest(1)" tool gained a "--repeat :" option to specify conditions in which to repeat tests. This generalizes the existing "--repeat-until-fail " option to add modes for "until-pass" and "after-timeout". * Target link properties "INTERFACE_LINK_OPTIONS", "INTERFACE_LINK_DIRECTORIES" and "INTERFACE_LINK_DEPENDS" are now transitive over private dependencies on static libraries. See policy "CMP0099". * When using MinGW tools, the "find_library()" command no longer finds ".dll" files by default. Instead, it expects ".dll.a" import libraries to be available. * The "Ninja" generator now prefers the first ninja build tool to appear in the "PATH" no matter whether it is called "ninja-build", "ninja", or "samu". Previously the first of those names to appear anywhere in the "PATH" would be preferred. * "cmake(1)" gained a "-E rm" command-line tool that can be used to remove directories and files. This supersedes the existing "-E remove" and "-E remove_directory" tools and has better semantics. CMake 3.17 Release Notes Changes made since CMake 3.16 include the following. New Features Generators -- * "cmake(1)" gained a "Ninja Multi-Config" generator, which is similar to the "Ninja" generator but can be used to build multiple configurations at once. * Visual Studio Generators learned to support per-config sources. Previously only Command-Line Build Tool Generators supported them. * Visual Studio Generators for VS 2010 and above now support specifying the "VCTargetsPath" value for project files in "CMAKE_GENERATOR_TOOLSET" setting. * Visual Studio Generators for VS 2010 and above learned to support .NET Standard and .NET Core. See the "DOTNET_TARGET_FRAMEWORK" target property and associated "CMAKE_DOTNET_TARGET_FRAMEWORK" variable. Languages - * The "Compile Features" functionality now offers meta-features for the CUDA language standard levels (e.g. "cuda_std_03", "cuda_std_14"). See "CMAKE_CUDA_KNOWN_FEATURES". Compilers - * The IBM XL Fortran compiler is now supported by the "Ninja" generator. Command-Line * "cmake(1)" gained a "--debug-find" command-line option to enable additional human-readable output on where "find_*" commands search. * "cmake(1)" gained a "--trace-format" command-line option that can be used to set the "--trace" output format. Currently, the old human readable and the new JSON format are supported. The new JSON format is easier to parse automatically than the existing format. * "cmake(1)" gained a "-E rm" command-line tool that can be used to remove directories and files. This supersedes the existing "-E remove" and "-E remove_directory" tools and has better semantics. Commands * The "add_custom_command()" command learned to interpret paths in "DEPENDS" arguments that are specified relative to the current binary directory. * The "foreach()" command learned a new "ZIP_LISTS" option
[cmake-developers] [ANNOUNCE] CMake 3.13.3 available for download
We are pleased to announce that CMake 3.13.3 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
* The VS 2017 generator has been fixed to work when VS 2019 is installed.
-
Changes in 3.13.3 since 3.13.2:
Brad King (4):
VS: Exclude VS 2019 instances when using VS 2017 generator
Tests: Add cases for -{C,D,U} without a source tree
Tests: Add case for warning when AUTOMOC/UIC/RCC gets disabled
CMake 3.13.3
Craig Scott (2):
cmake: Stop processing if -P option lacks file name
cmake: Ensure source and binary dirs are set
Paul Seyfert (1):
cmake: distinguish '-Cpath' from '-C path' in source dir parsing
Sebastian Holtermann (1):
Autogen: Issue a warning when AUTOMOC/UIC/RCC gets disabled.
Tim Blechmann (1):
BundleUtilities: Ensure target dir exists when creating symlinks
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] cmake.org, gitlab.kitware.com, dashboard downtime
Cmake Devs, Kitware NY is moving into a new office building on Dec 15th. This involves moving the company's network and testing infrastructure. As a result, there will be downtime for dashboard machines starting on Dec 13th, and websites starting on Dec 15th. Expect cmake.org, cmake.org/cmake/help/, open.cdash.org, and gitlab.kitware.com to be unavailable all day Dec. 15th while we physically move everything and complete the network cutover. Expect dashboards to start coming online on Dec 17th. There is a good chance of network connectivity being unstable for a few days afterwards while we troubleshoot and fix any issues. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.13.1 available for download
We are pleased to announce that CMake 3.13.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.13.1 since 3.13.0: Brad King (3): Fortran: Fix module dependency scanning with upper-case SUBMODULE FindBoost: Restore finding without CXX language enabled CMake 3.13.1 Harry Mallon (1): VS: Avoid crash with VS 2015 when all SDKs are higher than 10.0.14393.0 Sebastian Holtermann (1): Autogen: Fix empty uic executable string -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
Re: [cmake-developers] $LIST_LENGTH{} syntax (was: Support for list length expression in if()-command?)
I like some syntax that looks like $LEN{}.
I would love to keep the $...{ syntax open for future exentsion such
as easy target property set/get ( $[prop_name]{target} ) . This seems
to be okay as $ENV, and $CACHE only work on variables, so therefore
adding $LEN that also only works on variables seems reasonable.
On Tue, Jan 22, 2019 at 7:46 AM Brad King via cmake-developers
wrote:
>
> On 1/22/19 7:40 AM, Daniel Franke wrote:
> > Whats about a Syntax like
> >
> > ${list::LENGTH}
>
> That would require dispatch after matching `${VAR}` syntax, and
> that lookup is one of the hottest paths according to profiling.
> We already have $ENV{} and $CACHE{} syntax.
>
> -Brad
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake-developers
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.14.1 available for download
We are pleased to announce that CMake 3.14.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.14.1 since 3.14.0: Brad King (11): VS: Fix x64 host recognition by x86 cmake process find_program: Restore leading double slash on Windows network path Eclipse: Fix extra generator to not crash on interface libraries ARMCC: Fix identification of ARM compiler when it defines GNU macros Help: Clarify policy CMP0082 documentation Restore support for include_directories() in toolchain files CUDA: Tolerate square brackets in PROMPT environment variable cmake: Fix '-E copy foo .' to avoid clobbering file FindFontconfig: Convert module variables to camel case ParseImplicitIncludeInfo: Canonicalize implicit include dirs CMake 3.14.1 Clément Rezvoy (1): CPackIFW: Add missing cpack_ifw_configure_component_group option processing Marc Chevrier (1): FindPython*: ensure correct architecture is selected. Sebastian Holtermann (1): Autogen: Do not treat hard-coded -I/usr/include exclusion as implicit include Sylvain Joubert (1): ctest_coverage: fix out-of-bounds index in Jacoco parser -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.14.0-rc3 is ready for testing
t. The "paxr" value will be mapped to "gnutar" and a deprecation message emitted. * CMake no longer issues a warning if a target listed in an "install(TARGETS)" command has its "EXCLUDE_FROM_ALL" property set to true. Changes made since CMake 3.14.0-rc2: Brad King (17): Prefix implicit include directories with sysroot on construction Restore unconditional use of "standard" include directories Do not explicitly report "standard" include directories as implicit Use -? instead of /? to test compiler for MSVC-like command-line support VS: Factor out a method to set the Windows SDK version internally VS: Tell VS 2019 to use Windows SDK 8.1 explicitly when needed Fortran: Do not suppress explicit use of implicit include directories Tests: Restore support for CMake 3.1 through 3.6 with MSVC FindThreads: Fix libc check to use proper header for pthread_kill VS: Fix detection of clang-cl with -T llvm include_external_msproject: Restore support for EXCLUDE_FROM_ALL FindOctave: Remove module pending further work FindThreads: Revert libc symbol check to pthread_create VS: Drop workaround needed only for VS 2019 preview 2 and 3 Help: Update VS 2019 generator release note for preview 4 ExternalProject: Restore default log dir with custom stamp dir CMake 3.14.0-rc3 Christian Pfeiffer (1): FindJNI: Unify path search, fix support for Java 9 Craig Scott (12): Help: Remove outdated statement about get_filename_component() Help: Clarify and improve readability of link-related file subcommands Release notes: Make ExternalProject dot points consistent Help: Clarify ExternalProject_Add()'s LOG_MERGED_STDOUTERR behavior EXCLUDE_FROM_ALL: Don't warn if installing target excluded from all CheckLangSourceRuns: Capture run output to log files Help: User-provided variable names for try_* commands Help: try_compile() readability and grammar improvements Help: Consistency in try_compile() docs for target type Help: Caveat for try_compile() and CMAKE_TRY_COMPILE_PLATFORM_VARIABLES Help: Add release note for new ARCH_INDEPENDENT option Help: Fix minor inaccuracies of what BUILD_RPATH_USE_ORIGIN affects Kyle Edwards (1): CMAKE_ROLE: Fix value in --build for Visual Studio generators Maikel van den Hurk (1): Add ASM Compiler detection for QCC Marc Chevrier (1): PIE link options: No warning when policy CMP0083 is not set. Mathieu Garaud (1): Extend C++17/C++14 feature checks to cover more standard library APIs Paul Seyfert (1): Help: Fix --build-and-test synopsis in ctest(1) Robert Maynard (1): CUDA: Filter out -framework arguments during device linking Sebastian Holtermann (2): Autogen: Add output caching GetExecutableTestOutput Autogen: Use output caching GetExecutableTestOutput Yves Frederix (1): FindBoost: Find boost libraries built with --layout=tagged -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.14.0 available for download
I am happy to announce that CMake 3.14.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.14
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.14/release/3.14.html
Some of the more significant changes in CMake 3.14 are:
* Support for running CMake on Windows XP and Windows Vista has been
dropped. The precompiled Windows binaries provided on "cmake.org"
now require Windows 7 or higher.
* CMake now supports Cross Compiling for iOS, tvOS, or watchOS using
simple toolchain files.
* The "Visual Studio 16 2019" generator was added. This is
experimental and based on "Visual Studio 2019 Preview 4" because
this version of VS has not been released.
The VS 2019 generator differs from generators for earlier versions
in that it does not provide variants that specify the target
platform in the generator name. Instead "CMAKE_GENERATOR_PLATFORM"
must be used, e.g. through the "-A" command-line option.
Furthermore, the default target platform (architecture) is now based
on the *host* platform. The VS host toolset selection is now based
on the host architecture as well.
* The "Green Hills MULTI" generator has been updated to include Object
Library support, support for target renaming and destination output
control properties, and other improvements.
* A "CMAKE_BUILD_RPATH_USE_ORIGIN" variable and corresponding
"BUILD_RPATH_USE_ORIGIN" target property were added to enable use of
relative runtime paths (RPATHs). This helps achieving relocatable
and reproducible builds that are invariant of the build directory.
* The "install(TARGETS)" command learned how to install to an
appropriate default directory for a given target type, based on
variables from the "GNUInstallDirs" module and built-in defaults, in
lieu of a "DESTINATION" argument.
* The "install(FILES)" and "install(DIRECTORY)" commands learned a
new set of parameters for installing files as a file type, setting
the destination based on the appropriate variables from
"GNUInstallDirs" and built-in defaults, in lieu of a "DESTINATION"
argument.
* The "install(CODE)" and "install(SCRIPT)" commands learned to
support generator expressions. See policy "CMP0087".
* The "if()" command gained support for checking if cache variables
are defined with the "DEFINED CACHE{VAR}" syntax.
* A file-based api for clients to get semantic buildsystem
information has been added. See the "cmake-file-api(7)" manual.
This is intended to replace the "cmake-server(7)" mode for IDEs.
* The "cmake(1)" Build Tool Mode ("cmake --build") gained "--
verbose" and "-v" options to specify verbose build output. Some
generators such as Xcode don't support this option currently.
* The "cmake(1)" "-E compare_files" command learned a new "--ignore-
eol" option to specify that end-of-line differences (e.g. LF vs
CRLF) should be ignored when comparing files.
CMake 3.14 Release Notes
Changes made since CMake 3.13 include the following.
New Features
Generators
--
* The "Visual Studio 16 2019" generator was added. This is
experimental and based on "Visual Studio 2019 Preview 4" because
this version of VS has not been released.
The VS 2019 generator differs from generators for earlier versions
in that it does not provide variants that specify the target
platform in the generator name. Instead "CMAKE_GENERATOR_PLATFORM"
must be used, e.g. through the "-A" command-line option.
Furthermore, the default target platform (architecture) is now based
on the *host* platform. The VS host toolset selection is now based
on the host architecture as well.
* The "Green Hills MULTI" generator has been updated:
* Now supports Object Libraries.
* Now warns on unsupported project types such as shared libraries.
* Now generates a top-level ".top.gpj" for each
directory calling the "project()" command. The top-level project
file "default.gpj" is no longer created.
* Now honors target renaming and destination output control
properties such as "RUNTIME_OUTPUT_DIRECTORY" and "OUTPUT_NAME".
This also fixes support for installation rules generated by
"install()".
* Now honors source file properties "INCLUDE_DIRECTORIES",
"COMPILE_DEFINITIONS", and "COMPILE_OPTIONS".
* Now supports Dynamic Download Integrity Applications which did
not include Integrate Files via "GHS_INTEGRITY_APP" and setting a
target link flag of "-dynamic".
* The contents of project files now sorts sources groups and files
by name. Set the "GHS_NO_SOURCE_GROUP_FILE" target property to
"ON" to generate a single project file for the target instead of a
project file for each source group. Set the
"CMAKE_GHS_NO_SOURCE_GROUP_FILE" variable to enable this for all
targets.
File-Based API
--
* A file-based api for
[cmake-developers] [ANNOUNCE] CMake 3.14.0-rc4 is ready for testing
I am proud to announce the fourth CMake 3.14 release candidate.
https://cmake.org/download/
The first two 3.14.0 release candidates included the FindOcatave
module. This has been removed in rc3, and rc4 pending further
development.
Documentation is available at:
https://cmake.org/cmake/help/v3.14
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.14/release/3.14.html
Some of the more significant changes in CMake 3.14 are:
* Support for running CMake on Windows XP and Windows Vista has been
dropped. The precompiled Windows binaries provided on "cmake.org"
now require Windows 7 or higher.
* CMake now supports Cross Compiling for iOS, tvOS, or watchOS using
simple toolchain files.
* The "Visual Studio 16 2019" generator was added. This is
experimental and based on "Visual Studio 2019 Preview 4" because
this version of VS has not been released.
The VS 2019 generator differs from generators for earlier versions
in that it does not provide variants that specify the target
platform in the generator name. Instead "CMAKE_GENERATOR_PLATFORM"
must be used, e.g. through the "-A" command-line option.
Furthermore, the default target platform (architecture) is now based
on the *host* platform. The VS host toolset selection is now based
on the host architecture as well.
* The "Green Hills MULTI" generator has been updated to include Object
Library support, support for target renaming and destination output
control properties, and other improvements.
* A "CMAKE_BUILD_RPATH_USE_ORIGIN" variable and corresponding
"BUILD_RPATH_USE_ORIGIN" target property were added to enable use of
relative runtime paths (RPATHs). This helps achieving relocatable
and reproducible builds that are invariant of the build directory.
* The "install(TARGETS)" command learned how to install to an
appropriate default directory for a given target type, based on
variables from the "GNUInstallDirs" module and built-in defaults, in
lieu of a "DESTINATION" argument.
* The "install(FILES)" and "install(DIRECTORY)" commands learned a
new set of parameters for installing files as a file type, setting
the destination based on the appropriate variables from
"GNUInstallDirs" and built-in defaults, in lieu of a "DESTINATION"
argument.
* The "install(CODE)" and "install(SCRIPT)" commands learned to
support generator expressions. See policy "CMP0087".
* The "if()" command gained support for checking if cache variables
are defined with the "DEFINED CACHE{VAR}" syntax.
* A file-based api for clients to get semantic buildsystem
information has been added. See the "cmake-file-api(7)" manual.
This is intended to replace the "cmake-server(7)" mode for IDEs.
* The "cmake(1)" Build Tool Mode ("cmake --build") gained "--
verbose" and "-v" options to specify verbose build output. Some
generators such as Xcode don't support this option currently.
* The "cmake(1)" "-E compare_files" command learned a new "--ignore-
eol" option to specify that end-of-line differences (e.g. LF vs
CRLF) should be ignored when comparing files.
CMake 3.14 Release Notes
Changes made since CMake 3.13 include the following.
New Features
Generators
--
* The "Visual Studio 16 2019" generator was added. This is
experimental and based on "Visual Studio 2019 Preview 4" because
this version of VS has not been released.
The VS 2019 generator differs from generators for earlier versions
in that it does not provide variants that specify the target
platform in the generator name. Instead "CMAKE_GENERATOR_PLATFORM"
must be used, e.g. through the "-A" command-line option.
Furthermore, the default target platform (architecture) is now based
on the *host* platform. The VS host toolset selection is now based
on the host architecture as well.
* The "Green Hills MULTI" generator has been updated:
* Now supports Object Libraries.
* Now warns on unsupported project types such as shared libraries.
* Now generates a top-level ".top.gpj" for each
directory calling the "project()" command. The top-level project
file "default.gpj" is no longer created.
* Now honors target renaming and destination output control
properties such as "RUNTIME_OUTPUT_DIRECTORY" and "OUTPUT_NAME".
This also fixes support for installation rules generated by
"install()".
* Now honors source file properties "INCLUDE_DIRECTORIES",
"COMPILE_DEFINITIONS", and "COMPILE_OPTIONS".
* Now supports Dynamic Download Integrity Applications which did
not include Integrate Files via "GHS_INTEGRITY_APP" and setting a
target link flag of "-dynamic".
* The contents of project files now sorts sources groups and files
by name. Set the "GHS_NO_SOURCE_GROUP_FILE" target property to
"ON" to generate a single project file for the target instead of a
project file for each source group. Set the
[cmake-developers] [ANNOUNCE] CMake 3.14.0-rc1 is ready for testing
I am proud to announce the first CMake 3.14 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.14
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.14/release/3.14.html
Some of the more significant changes in CMake 3.14 are:
* Support for running CMake on Windows XP and Windows Vista has been
dropped. The precompiled Windows binaries provided on "cmake.org"
now require Windows 7 or higher.
* CMake now supports Cross Compiling for iOS, tvOS, or watchOS using
simple toolchain files.
* The "Visual Studio 16 2019" generator was added. This is
experimental and based on "Visual Studio 2019 Preview 2" because
this version of VS has not been released.
The VS 2019 generator differs from generators for earlier versions
in that it does not provide variants that specify the target
platform in the generator name. Instead "CMAKE_GENERATOR_PLATFORM"
must be used, e.g. through the "-A" command-line option.
Furthermore, the default target platform (architecture) is now based
on the *host* platform. The VS host toolset selection is now based
on the host architecture as well.
* A "CMAKE_BUILD_RPATH_USE_ORIGIN" variable and corresponding
"BUILD_RPATH_USE_ORIGIN" target property were added to enable use of
relative runtime paths (RPATHs). This helps achieving relocatable
and reproducible builds that are invariant of the build directory.
* The "install(TARGETS)" command learned how to install to an
appropriate default directory for a given target type, based on
variables from the "GNUInstallDirs" module and built-in defaults, in
lieu of a "DESTINATION" argument.
* The "install(FILES)" and "install(DIRECTORY)" commands learned a
new set of parameters for installing files as a file type, setting
the destination based on the appropriate variables from
"GNUInstallDirs" and built-in defaults, in lieu of a "DESTINATION"
argument.
* The "install(CODE)" and "install(SCRIPT)" commands learned to
support generator expressions. See policy "CMP0087".
* The "if()" command gained support for checking if cache variables
are defined with the "DEFINED CACHE{VAR}" syntax.
* A file-based api for clients to get semantic buildsystem
information has been added. See the "cmake-file-api(7)" manual.
This is intended to replace the "cmake-server(7)" mode for IDEs.
* The "cmake(1)" Build Tool Mode ("cmake --build") gained "--
verbose" and "-v" options to specify verbose build output. Some
generators such as Xcode don't support this option currently.
* The "cmake(1)" "-E compare_files" command learned a new "--ignore-
eol" option to specify that end-of-line differences (e.g. LF vs
CRLF) should be ignored when comparing files.
CMake 3.14 Release Notes
Changes made since CMake 3.13 include the following.
New Features
Generators
--
* The "Visual Studio 16 2019" generator was added. This is
experimental and based on "Visual Studio 2019 Preview 2" because
this version of VS has not been released.
The VS 2019 generator differs from generators for earlier versions
in that it does not provide variants that specify the target
platform in the generator name. Instead "CMAKE_GENERATOR_PLATFORM"
must be used, e.g. through the "-A" command-line option.
Furthermore, the default target platform (architecture) is now based
on the *host* platform. The VS host toolset selection is now based
on the host architecture as well.
File-Based API
--
* A file-based api for clients to get semantic buildsystem
information has been added. See the "cmake-file-api(7)" manual.
This is intended to replace the "cmake-server(7)" mode for IDEs.
Platforms
-
* CMake now supports Cross Compiling for iOS, tvOS, or watchOS using
simple toolchain files.
Command-Line
* The "cmake(1)" Build Tool Mode ("cmake --build") gained "--
verbose" and "-v" options to specify verbose build output. Some
generators such as Xcode don't support this option currently.
* The "cmake(1)" "-E compare_files" command learned a new "--ignore-
eol" option to specify that end-of-line differences (e.g. LF vs
CRLF) should be ignored when comparing files.
* The "cmake-gui(1)" dialog gained new "-S" and "-B" arguments to
explicitly specify source and build directories.
Commands
* The "file()" command learned a new sub-command, "READ_SYMLINK",
which can be used to determine the path that a symlink points to.
* The "file()" command gained a "SIZE" mode to get the size of a
file on disk.
* The "find_package()" command learned to optionally resolve
symbolic links in the paths to package configuration files. See the
"CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS" variable.
* The "get_filename_component()" command gained new "LAST_EXT" and
"NAME_WLE" variants to work with the extension after the last "." in
[cmake-developers] [ANNOUNCE] CMake 3.14.0-rc2 is ready for testing
I am proud to announce the second CMake 3.14 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.14
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.14/release/3.14.html
Some of the more significant changes in CMake 3.14 are:
* Support for running CMake on Windows XP and Windows Vista has been
dropped. The precompiled Windows binaries provided on "cmake.org"
now require Windows 7 or higher.
* CMake now supports Cross Compiling for iOS, tvOS, or watchOS using
simple toolchain files.
* The "Visual Studio 16 2019" generator was added. This is
experimental and based on "Visual Studio 2019 Preview 2" because
this version of VS has not been released.
The VS 2019 generator differs from generators for earlier versions
in that it does not provide variants that specify the target
platform in the generator name. Instead "CMAKE_GENERATOR_PLATFORM"
must be used, e.g. through the "-A" command-line option.
Furthermore, the default target platform (architecture) is now based
on the *host* platform. The VS host toolset selection is now based
on the host architecture as well.
* The "Green Hills MULTI" generator has been updated to include Object
Library support, support for target renaming and destination output
control properties, and other improvements.
* A "CMAKE_BUILD_RPATH_USE_ORIGIN" variable and corresponding
"BUILD_RPATH_USE_ORIGIN" target property were added to enable use of
relative runtime paths (RPATHs). This helps achieving relocatable
and reproducible builds that are invariant of the build directory.
* The "install(TARGETS)" command learned how to install to an
appropriate default directory for a given target type, based on
variables from the "GNUInstallDirs" module and built-in defaults, in
lieu of a "DESTINATION" argument.
* The "install(FILES)" and "install(DIRECTORY)" commands learned a
new set of parameters for installing files as a file type, setting
the destination based on the appropriate variables from
"GNUInstallDirs" and built-in defaults, in lieu of a "DESTINATION"
argument.
* The "install(CODE)" and "install(SCRIPT)" commands learned to
support generator expressions. See policy "CMP0087".
* The "if()" command gained support for checking if cache variables
are defined with the "DEFINED CACHE{VAR}" syntax.
* A file-based api for clients to get semantic buildsystem
information has been added. See the "cmake-file-api(7)" manual.
This is intended to replace the "cmake-server(7)" mode for IDEs.
* The "cmake(1)" Build Tool Mode ("cmake --build") gained "--
verbose" and "-v" options to specify verbose build output. Some
generators such as Xcode don't support this option currently.
* The "cmake(1)" "-E compare_files" command learned a new "--ignore-
eol" option to specify that end-of-line differences (e.g. LF vs
CRLF) should be ignored when comparing files.
CMake 3.14 Release Notes
Changes made since CMake 3.13 include the following.
New Features
Generators
--
* The "Visual Studio 16 2019" generator was added. This is
experimental and based on "Visual Studio 2019 Preview 2" because
this version of VS has not been released.
The VS 2019 generator differs from generators for earlier versions
in that it does not provide variants that specify the target
platform in the generator name. Instead "CMAKE_GENERATOR_PLATFORM"
must be used, e.g. through the "-A" command-line option.
Furthermore, the default target platform (architecture) is now based
on the *host* platform. The VS host toolset selection is now based
on the host architecture as well.
* The "Green Hills MULTI" generator has been updated:
* Now supports Object Libraries.
* Now warns on unsupported project types such as shared libraries.
* Now generates a top-level ".top.gpj" for each
directory calling the "project()" command. The top-level project
file "default.gpj" is no longer created.
* Now honors target renaming and destination output control
properties such as "RUNTIME_OUTPUT_DIRECTORY" and "OUTPUT_NAME".
This also fixes support for installation rules generated by
"install()".
* Now honors source file properties "INCLUDE_DIRECTORIES",
"COMPILE_DEFINITIONS", and "COMPILE_OPTIONS".
* Now supports Dynamic Download Integrity Applications which did
not include Integrate Files via "GHS_INTEGRITY_APP" and setting a
target link flag of "-dynamic".
* The contents of project files now sorts sources groups and files
by name. Set the "GHS_NO_SOURCE_GROUP_FILE" target property to
"ON" to generate a single project file for the target instead of a
project file for each source group. Set the
"CMAKE_GHS_NO_SOURCE_GROUP_FILE" variable to enable this for all
targets.
File-Based API
--
* A file-based api for clients to get
Re: [cmake-developers] [vtk-developers] CDash frontend refresh
My feeling on this is that the green should be stronger color. A fully green dashboard is a happy thing and it should make me the viewer happy :) I do get some less than ideal spacing and alignment ( see attached image ) around the `Items per page` and the `feed` On Thu, Jan 31, 2019 at 3:13 PM Dan Lipsa via vtk-developers wrote: > > Maybe the problem is the white text? > There isn't enough difference between the fairly pale color (red, yellow) and > the text color. > > Changing the text color to black might make it more readable and will make > the text that shows the number of errors (or warnings) consistent. > > On Thu, Jan 31, 2019 at 3:00 PM TJ Corona via vtk-developers > wrote: >> >> Hi Zack, >> >> I like the new layout! It’s very clean. Would it be possible to add an >> option to use the original table colors (green, yellow, red)? I can’t put my >> finger on why, but I find the new color palette more difficult to read. >> >> Sincerely, >> T.J. >> >> On Jan 31, 2019, at 1:53 PM, Zack Galbreath via vtk-developers >> wrote: >> >> We've been working on a refresh of CDash's look and feel. Before rolling >> this out, we wanted to give you all a sneak peek so that you could let us >> know what you think. >> >> Our proposed changes are now live on http://testing.cdash.org, which shares >> a backend database with https://open.cdash.org. >> >> For example, >> old: https://open.cdash.org/index.php?project=VTK >> new: http://testing.cdash.org/index.php?project=VTK >> >> This is inevitably a work in progress so future tweaks should be expected. >> That being said, please let us know if you see anything that seems like an >> obvious defect to you. >> ___ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q=vtk-developers >> >> Follow this link to subscribe/unsubscribe: >> https://vtk.org/mailman/listinfo/vtk-developers >> >> >> ___ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q=vtk-developers >> >> Follow this link to subscribe/unsubscribe: >> https://vtk.org/mailman/listinfo/vtk-developers >> > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=vtk-developers > > Follow this link to subscribe/unsubscribe: > https://vtk.org/mailman/listinfo/vtk-developers > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.13.4 available for download
We are pleased to announce that CMake 3.13.4 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.13.4 since 3.13.3: Ben Boeckel (2): Tests: add cases for providing Qt5Core_VERSION manually AutoGen: query Qt5 version from directory properties Brad King (5): Revert "file: Allow DOWNLOAD/UPLOAD using alternate authentication methods" Intel: Record support for relaxed constexpr by version 18.0.5 macOS: Restore compatibility for setting FRAMEWORK after install() FindLAPACK: Distinguish check result variable name from FindBLAS CMake 3.13.4 Chuck Atkins (1): macOS: Add missing explicit dependency on CoreServices framework Craig Scott (3): cmake: Convert no source/build dir error to warning Help: Add 3.13.4 release note for no source/build dir error/warning FindDoxygen: Escape backslashes in default values -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.14.2 available for download
We are pleased to announce that CMake 3.14.2 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.14.2 since 3.14.1: Brad King (9): MSVC: Fix MSVC_TOOLSET_VERSION for VS 2019 v142 toolset ARMCC: Do not identify ARMClang as ARMCC IRSL: Fix discovery of VS 2019 v142 toolset redistributables Tests: Clarify hand-written cases in RunCMake.ParseImplicitIncludeInfo Tests: Teach RunCMake.ParseImplicitIncludeInfo to match output by regex Fix implicit include directory extraction for adaptive relative paths Xcode: Factor out duplicate source group code into lambda Xcode: Avoid mutating App Bundle targets during generation CMake 3.14.2 Julien Jomier (1): cmake-gui: Fix icon overlay on windows Regina Pfeifer (1): Modules/CTest: Fix SubmitURL mistersandman (1): cmake-gui: Fix theme on Windows with Qt >= 5.10 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.15.0-rc1 is ready for testing
I am proud to announce the first CMake 3.15 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.15 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.15/release/3.15.html Some of the more significant changes in CMake 3.15 are: * The "CMAKE_MSVC_RUNTIME_LIBRARY" variable and "MSVC_RUNTIME_LIBRARY" target property were introduced to select the runtime library used by compilers targeting the MSVC ABI. See policy "CMP0091". * With MSVC-like compilers the value of "CMAKE__FLAGS" no longer contains warning flags like "/W3" by default. See policy "CMP0092". * The "Clang" compiler variant on Windows that targets the MSVC ABI but has a GNU-like command line is now supported. * Preliminary support for the "Swift" language was added to the "Ninja" generator. * The "$" generator expression was introduced to allow specification of compile options for target files based on the "CMAKE__COMPILER_ID" and "LANGUAGE" of each source file. * The "generator expressions" "C_COMPILER_ID", "CXX_COMPILER_ID", "CUDA_COMPILER_ID", "Fortran_COMPILER_ID", "COMPILE_LANGUAGE", "COMPILE_LANG_AND_ID", and "PLATFORM_ID" learned to support matching one value from a comma-separated list. * The "CMAKE_FIND_PACKAGE_PREFER_CONFIG" variable was added to tell "find_package()" calls to look for a package configuration file first even if a find module is available. * The "PUBLIC_HEADER" and "PRIVATE_HEADER" properties may now be set on Interface Libraries. The headers specified by those properties can be installed using the "install(TARGETS)" command by passing the "PUBLIC_HEADER" and "PRIVATE_HEADER" arguments respectively. * The "CMAKE_VS_JUST_MY_CODE_DEBUGGING" variable and "VS_JUST_MY_CODE_DEBUGGING" target property were added to enable the Just My Code feature of the Visual Studio Debugger when compiling with MSVC cl 19.05 and higher. * The "FindBoost" module was reworked to expose a more consistent user experience between its “Config” and “Module” modes and with other find modules in general. * The "message()" command learned new types: "NOTICE", "VERBOSE", "DEBUG" and "TRACE". * The "export(PACKAGE)" command now does nothing unless enabled via "CMAKE_EXPORT_PACKAGE_REGISTRY". See policy "CMP0090". * The "CMAKE_GENERATOR" environment variable was added to specify a default generator to use when "cmake(1)" is run without a "-G" option. Additionally, environment variables "CMAKE_GENERATOR_PLATFORM", "CMAKE_GENERATOR_TOOLSET", and "CMAKE_GENERATOR_INSTANCE" were created to configure the generator. * The "cmake(1)" command gained a new "--install" option. This may be used after building a project to run installation without using the generated build system or the native build tool. * The "cmake(1)" command learned a new CLI option "--loglevel". * The "cmake-server(7)" mode has been deprecated and will be removed from a future version of CMake. Please port clients to use the "cmake-file-api(7)" instead. CMake 3.15 Release Notes Changes made since CMake 3.14 include the following. New Features Generators -- * The "Xcode" generator now supports per-target schemes. See the "CMAKE_XCODE_GENERATE_SCHEME" variable and "XCODE_GENERATE_SCHEME" target property. * The "Green Hills MULTI" generator has been updated: * It now supports the "add_custom_command()" and "add_custom_target()" commands. * It is now available on Linux. Languages - * Preliminary support for the "Swift" language was added to the "Ninja" generator: * Use the "SWIFTC" environment variable to specify a compiler. * The "Swift_DEPENDENCIES_FILE" target property and "Swift_DEPENDENCIES_FILE" source file property were added to customize dependency files. * The "Swift_MODULE_NAME" target property was added to customize the Swift module name. * The "Swift_DIAGNOSTICS_FILE" source property was added to indicate where to write the serialised Swift diagnostics. The Swift support is experimental, not considered stable, and may change in future releases of CMake. Compilers - * The "Clang" compiler variant on Windows that targets the MSVC ABI but has a GNU-like command line is now supported. * Support for the Clang-based ARM compiler was added with compiler id "ARMClang". * Support was added for the IAR compiler architectures Renesas RX, RL78, RH850 and Texas Instruments MSP430. * Support was added for the IAR compilers built for Linux (IAR BuildLx). Command-Line * The "CMAKE_GENERATOR" environment variable was added to specify a default generator to use when "cmake(1)" is run without a "-G" option. Additionally, environment variables "CMAKE_GENERATOR_PLATFORM", "CMAKE_GENERATOR_TOOLSET", and "CMAKE_GENERATOR_INSTANCE" were created to configure the generator.
[cmake-developers] [ANNOUNCE] CMake 3.14.5 available for download
We are pleased to announce that CMake 3.14.5 is now available for download. The Visual Studio 2019 16.1 update introduced a regression in MSBuild's evaluation of custom command dependencies causing them to re-run on every build. CMake 3.14.5 includes a workaround, for more details on the issue see: https://gitlab.kitware.com/cmake/cmake/issues/19303 Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.14.5 since 3.14.4: Alex Turbov (1): FindBoost: Add compiler features for Boost Contract library Brad King (5): libarchive: avoid b64_encode name conflict with Solaris built-in function FindThreads: Drop incorrect docs about usage with C++ Do not exclude include directories made implicit by CPATH VS: Isolate custom command input/output generation scopes CMake 3.14.5 Frans van Dorsselaer (2): VS: Clarify name of custom commands AdditionalInputs variable VS: De-duplicate custom command dependencies -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.13.5 available for download
We are pleased to announce that CMake 3.13.5 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.13.5 since 3.13.4: Brad King (3): target_link_libraries: Fix static library private deps in other dirs Help: Add 3.13.5 release notes CMake 3.13.5 Nils Gladitz (1): CMake: Fix WiX installer downgrades with versioned binaries -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.14.4 available for download
We are pleased to announce that CMake 3.14.4 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.14.4 since 3.14.3: Alex Turbov (2): FindBoost: Record compiler features for Boost 1.67 and above FindBoost: Fix compiler features for `fiber` and `context` Alexandru Croitor (1): iOS: Fix try_compile FILE_COPY not to fail Brad King (3): target_link_libraries: Fix static library private deps in other dirs Help: Add 3.14.4 release notes CMake 3.14.4 Daniele E. Domenichelli (1): FindSWIG: Support swig4.0 Gregor Jasny (2): Apple: Preserve high resolution mtime for static libraries Apple: Properly lookup XCTest for iOS and tvOS Marc Chevrier (2): FindPython: NumPy: fix erroneous dependencies management FindPython: ensure variable Python_RUNTIME_LIBRARY_DIRS is set correctly -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.14.3 available for download
We are pleased to announce that CMake 3.14.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.14.3 since 3.14.2: Ben Boeckel (1): FindOpenGL: look for GLVND libraries with a libglvnd suffix Brad King (4): FindBoost: Add support for MSVC toolset version 14.2 IRSL: Update redist directory for VS 2019 update 1 VS: Provide the default platform name to project code CMake 3.14.3 Christian Pfeiffer (1): FindQt3: Restore missing lib and bin path suffixes Rolf Eike Beer (1): FindBoost: Fix detection with version suffixes on Gentoo -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.15.3 available for download
We are pleased to announce that CMake 3.15.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.3 since 3.15.2: Brad King (13): Flang: Implement MSVC runtime library abstraction CTest: Fix --show-only=json-v1 output with REQUIRED_FILES property cmGlobalGenerator: Fix CheckCompilerIdCompatibility local var lifetime cmAffinity: Add include for CPU_ZERO on Alpine Linux find_path: Fix crash on empty old-style list of names fileapi: Fix codemodel v2 target file name for CMP0037 OLD behavior FindBoost: Simplify conditional block for last known version FindBoost: Remove incorrect 1.70 timer dependency FindBoost: Unwrap compatibility INTERFACE targets for legacy variables FindBoost: Add support for Boost 1.71 FindBoost: Clarify role of legacy variables in warning message FindBoost: Tolerate future Boost INTERFACE libraries CMake 3.15.3 Chuck Atkins (1): CrayPrgEnv: Change default linking mode based on PE version M Furkan USLU (1): ccmake: handle cache entries with empty STRINGS property Marvin Schmidt (1): libarchive: We now require at least version 3.3.3 Robert Maynard (1): FindMPI: Restore MPI__COMPILE_FLAGS and MPI__COMPILE_OPTIONS Sebastian Holtermann (3): Ninja: Add support for ADDITIONAL_CLEAN_FILES in custom targets Tests: Extend MakeClean test to test various target types Autogen: Fix AUTOUIC segfault, when file includes colliding ui_*.h file -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.14.7 available for download
We are pleased to announce that CMake 3.14.7 is now available for download. This release fixes a regression in EXCLUDE_FROM_ALL. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.14.7 since 3.14.6: Brad King (6): Tests: Teach RunCMake to support a custom working directory Tests: Revise RunCMake.add_subdirectory ExcludeFromAll to avoid globbing Tests: Clarify target names in RunCMake.add_subdirectory ExcludeFromAll Restore "all" target in subdirectories marked EXCLUDE_FROM_ALL Help: Add release note for EXCLUDE_FROM_ALL fix in 3.14.7 CMake 3.14.7 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.15.4 available for download
We are pleased to announce that CMake 3.15.4 is now available for download. This release fixes a regression in EXCLUDE_FROM_ALL. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.4 since 3.15.3: Brad King (10): VS: Tell VS 16.4 not to verify SYMBOLIC custom command outputs Tests: Teach RunCMake to support a custom working directory Tests: Revise RunCMake.add_subdirectory ExcludeFromAll to avoid globbing Tests: Clarify target names in RunCMake.add_subdirectory ExcludeFromAll Makefiles: Revert "Make build root targets ... recursive" Restore "all" target in subdirectories marked EXCLUDE_FROM_ALL Help: Add release note for EXCLUDE_FROM_ALL fix in 3.14.7 Help: Add release note for EXCLUDE_FROM_ALL fix in 3.15.4 Help: Mention 3.14.7 EXCLUDE_FROM_ALL fix in 3.15.4 release note CMake 3.15.4 LE GARREC Vincent (1): Help: Document VS 2019 toolset in MSVC_TOOLSET_VERSION -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake Discourse forum now available
A Discourse forum is now available for the CMake community: https://discourse.cmake.org Discourse offers users more control over their level of participation, allowing them to subscribe or unsubscribe by category or individual topic. Users may choose to participate by web forum, email, or both. To get started, see our Forum Help page: https://discourse.cmake.org/faq User accounts may be created using Email Registration, a GitHub Account, or a Google Account. For those who prefer email over web forums, the Forum Help page includes instructions to participate in the forum purely via email. Creating topics in the forum via email (and receiving replies) is supported *with or without* registering a user account. User accounts may be configured to receive email notifications for forum activity at several levels of granularity, or to receive email notifications for all activity like a mailing list. To facilitate a transition period, the current mailman-based mailing lists will remain active until at least the end of March 2020, and their archives will remain available after that. See you on discourse.cmake.org! -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.16.0-rc3 is ready for testing
I am proud to announce the third CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more significant changes in CMake 3.16 are:
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
* The "target_precompile_headers()" command was added to specify a
list of headers to precompile for faster compilation times.
* The "UNITY_BUILD" target property was added to tell generators to
batch include source files for faster compilation times.
* The "find_file()", "find_library()", "find_path()",
"find_package()", and "find_program()" commands have learned to
check the following variables to control searching
* "CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH" - Controls the searching
the cmake-specific environment variables.
* "CMAKE_FIND_USE_CMAKE_PATH" - Controls the searching the cmake-
specific cache variables.
* "CMAKE_FIND_USE_CMAKE_SYSTEM_PATH" - Controls the searching
cmake platform specific variables.
* "CMAKE_FIND_USE_PACKAGE_ROOT_PATH" - Controls the searching of
"_ROOT" variables.
* "CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH" - Controls the
searching the standard system environment variables.
* The "file()" command learned a new sub-command,
"GET_RUNTIME_DEPENDENCIES", which allows you to recursively get the
list of libraries linked by an executable or library. This sub-
command is intended as a replacement for "GetPrerequisites".
* "ctest(1)" now has the ability to serialize tests based on
hardware requirements for each test. See Hardware Allocation for
details.
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One may manually enable runtime linking for shared libraries
and/or loadable modules by adding "-Wl,-G" to their link flags (e.g.
in the "CMAKE_SHARED_LINKER_FLAGS" or "CMAKE_MODULE_LINKER_FLAGS"
variable). One may manually enable runtime linking for executables
by adding "-Wl,-brtl" to their link flags (e.g. in the
"CMAKE_EXE_LINKER_FLAGS" variable).
* "cmake(1)" "-E" now supports "true" and "false" commands, which do
nothing while returning exit codes of 0 and 1, respectively.
* "cmake(1)" gained a "--trace-redirect=" command line option
that can be used to redirect "--trace" output to a file instead of
"stderr".
* The "cmake(1)" "--loglevel" command line option has been renamed
to "--log-level" to make it consistent with the naming of other
command line options. The "--loglevel" option is still supported to
preserve backward compatibility.
* The "CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY" variable has been
deprecated. Use the "CMAKE_FIND_USE_PACKAGE_REGISTRY" variable
instead.
* The "GetPrerequisites" module has been deprecated, as it has been
superceded by "file(GET_RUNTIME_DEPENDENCIES)".
CMake 3.16 Release Notes
Changes made since CMake 3.15 include the following.
New Features
Languages
-
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
Compilers
-
* The "Clang" compiler is now supported on "Solaris".
Platforms
-
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One
[cmake-developers] [ANNOUNCE] CMake 3.15.5 available for download
We are pleased to announce that CMake 3.15.5 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.5 since 3.15.4: Alan W. Irwin (1): Help: Fix COMPILE_LANG_AND_ID genex example Brad King (7): VS: Fix support for v142 toolset minor versions Xcode: Restore CMAKE_XCODE_GENERATE_SCHEME for custom targets VS: Tell VS 16.4 not to verify CMake-provided custom command outputs VS: Add toolset v142 CSharp flag table IRSL: Prefer MSVC runtime libraries from newest toolset first IRSL: Install vcruntime140_1.dll if available CMake 3.15.5 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.16.0-rc2 is ready for testing
I am proud to announce the second CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more significant changes in CMake 3.16 are:
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
* The "target_precompile_headers()" command was added to specify a
list of headers to precompile for faster compilation times.
* The "UNITY_BUILD" target property was added to tell generators to
batch include source files for faster compilation times.
* The "find_file()", "find_library()", "find_path()",
"find_package()", and "find_program()" commands have learned to
check the following variables to control searching
* "CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH" - Controls the searching
the cmake-specific environment variables.
* "CMAKE_FIND_USE_CMAKE_PATH" - Controls the searching the cmake-
specific cache variables.
* "CMAKE_FIND_USE_CMAKE_SYSTEM_PATH" - Controls the searching
cmake platform specific variables.
* "CMAKE_FIND_USE_PACKAGE_ROOT_PATH" - Controls the searching of
"_ROOT" variables.
* "CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH" - Controls the
searching the standard system environment variables.
* The "file()" command learned a new sub-command,
"GET_RUNTIME_DEPENDENCIES", which allows you to recursively get the
list of libraries linked by an executable or library. This sub-
command is intended as a replacement for "GetPrerequisites".
* "ctest(1)" now has the ability to serialize tests based on
hardware requirements for each test. See Hardware Allocation for
details.
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One may manually enable runtime linking for shared libraries
and/or loadable modules by adding "-Wl,-G" to their link flags (e.g.
in the "CMAKE_SHARED_LINKER_FLAGS" or "CMAKE_MODULE_LINKER_FLAGS"
variable). One may manually enable runtime linking for executables
by adding "-Wl,-brtl" to their link flags (e.g. in the
"CMAKE_EXE_LINKER_FLAGS" variable).
* "cmake(1)" "-E" now supports "true" and "false" commands, which do
nothing while returning exit codes of 0 and 1, respectively.
* "cmake(1)" gained a "--trace-redirect=" command line option
that can be used to redirect "--trace" output to a file instead of
"stderr".
* The "cmake(1)" "--loglevel" command line option has been renamed
to "--log-level" to make it consistent with the naming of other
command line options. The "--loglevel" option is still supported to
preserve backward compatibility.
* The "CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY" variable has been
deprecated. Use the "CMAKE_FIND_USE_PACKAGE_REGISTRY" variable
instead.
* The "GetPrerequisites" module has been deprecated, as it has been
superceded by "file(GET_RUNTIME_DEPENDENCIES)".
CMake 3.16 Release Notes
Changes made since CMake 3.15 include the following.
New Features
Languages
-
* CMake learned to support the Objective C ("OBJC") and Objective
C++ ("OBJCXX") languages. They may be enabled via the "project()"
and "enable_language()" commands. When "OBJC" or "OBJCXX" is
enabled, source files with the ".m" or ".mm", respectively, will be
compiled as Objective C or C++. Otherwise they will be treated as
plain C++ sources as they were before.
Compilers
-
* The "Clang" compiler is now supported on "Solaris".
Platforms
-
* On AIX, executables using the "ENABLE_EXPORTS" target property now
produce a linker import file with a ".imp" extension in addition to
the executable file. Plugins (created via "add_library()" with the
"MODULE" option) that use "target_link_libraries()" to link to the
executable for its symbols are now linked using the import file. The
"install(TARGETS)" command now installs the import file as an
"ARCHIVE" artifact.
* On AIX, runtime linking is no longer enabled by default. CMake
provides the linker enough information to resolve all symbols up
front. One
Re: [cmake-developers] [ANNOUNCE] CMake Discourse forum now available
> To facilitate a transition period, the current mailman-based mailing lists > will remain active until at least the end of March 2020, and their archives > will remain available after that. This transition period was announced both on the users list and here on the developers list. Since the developers list is fairly low traffic and there are not currently any active threads, we've decided to close this list now. Please post to the CMake Discourse "Development" category instead: https://discourse.cmake.org/c/development See you on discourse.cmake.org! -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware open-source projects at https://www.kitware.com/platforms Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers This mailing list is deprecated in favor of https://discourse.cmake.org
