[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

[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

[CMake] [ANNOUNCE] CMake 3.17.0-rc3 is ready for testing

I am proud to announce the third 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

[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:

[CMake] [ANNOUNCE] CMake 3.17.0-rc2 is ready for testing

I am proud to announce the second 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

[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

[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

[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:

[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:

[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:

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

[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:

[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:

[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:

[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

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

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. >

[CMake] [ANNOUNCE] CMake 3.16.0-rc4 is ready for testing

I am proud to announce the fourth 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

[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

[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

[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

[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

[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:

[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:

[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

[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

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,

Re: [CMake] Unity builds (was: Re: [ANNOUNCE] CMake 3.16.0-rc1 is ready for testing)

-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

[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

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

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

[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!

[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!

[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!

[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!

[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:

[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:

[CMake] [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

[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

[CMake] Free CMake course during KHQ Summer courses July 22-25 2019

Hi All, This summer between July 22 - 25th Kitware is offering 7 free courses over 3 days at our new headquarters in Albany NY. One of the free courses we will be offering is a full day CMake course on Tuesday July 23rd. Hopefully some of you will be able to attend, and we can meet in person.

Re: [CMake] Question about Variables

The `${ }` syntax deferences the variable, so what you are asking is if the variable `1_INC_PATH` exists. What you want is `if(DEFINED WITH_LIB_GLAD_INC_PATH)` to check for the existence of the variable `WITH_LIB_GLAD_INC_PATH` On Fri, May 31, 2019 at 4:11 PM Steven Truppe wrote: > > Hi

[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

[CMake] [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

Re: [CMake] Dependency cycle - why?

I misspoke. I meant that what you want to do with the custom commands was supported by CMake. Adding support for extra languages to CMake requires modifications at the C++ level, if you want full support. Things such as installing, and generator expressions require C++ level changes. On Sat, May

Re: [CMake] Dependency cycle - why?

Hi, The goal that you have is fully supported by CMake. You have just run into a bug in CMake, and you should report this to https://gitlab.kitware.com/cmake/cmake/issues . Basically at a very high level the name out the add_executable target `callback_generator` is the same as the internal name

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

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

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

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-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:

[CMake] [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:

[CMake] [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:

[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:

Re: [CMake] CMake with two C++ compilers

Currently we don't provide the compiler id and version for the CUDA host compiler. If you are interested in having this information can you please create an issue on the cmake gitlab: https://gitlab.kitware.com/cmake/cmake On Fri, May 10, 2019 at 12:09 PM JR Cary wrote: > > Thanks, Chuck. > > I

Re: [CMake] Support of compile features for Fujitsu C++ Compiler

The goal would be to upstream the compiler changes to cmake so that all users could benefit from the improved compiler detection :) I would look at the FindMPI docs on locating the correct mpi compiler: https://cmake.org/cmake/help/v3.14/module/FindMPI.html#variables-for-locating-mpi . It looks

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

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

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

[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

[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

Re: [CMake] CXX and CUDACXX

I don't have any other suggestions. In general I recommend the script approach or using enable_language(CUDA). The enable_language approach should work, so I am curious what other issues you are seeing. On Tue, Apr 16, 2019 at 2:24 PM Dustyn Blasig wrote: > > Thx for the info. > > Since CXX and

Re: [CMake] CXX and CUDACXX

The default implementation is to defer to CUDA for selecting what ever host compiler it would like. To make sure that CMake uses the same CXX and CUDACXX compiler you will need to explicitly state that either through the CUDAHOSTCXX env variable (

[CMake] [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:

[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:

Re: [CMake] Does enable_language(CUDA) still have the problem with reconfiguring?

Yes, we are dependent on the CUDA extensions for ms-build working correctly. On Mon, Apr 1, 2019 at 5:02 PM Mojca Miklavec wrote: > > On Mon, 1 Apr 2019 at 22:11, Robert Maynard via CMake wrote: > > > > For MSBuild we rely on the CUDA extensions written by nvidia which do >

Re: [CMake] Does enable_language(CUDA) still have the problem with reconfiguring?

It doesn't have this behavior. For Makefile and Ninja generators we get the proper header dependencies at compile time just like we do for C or C++. For MSBuild we rely on the CUDA extensions written by nvidia which do proper dependency tracking. On Sat, Mar 30, 2019 at 4:12 PM JR Cary wrote: >

[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:

[CMake] [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:

Re: [CMake] Strange issue with 3.14.0 and copying files

Just as a follow-up for the general community, this is a bug and can be tracked at: https://gitlab.kitware.com/cmake/cmake/issues/19075 On Wed, Mar 20, 2019 at 2:46 PM Ron Olson wrote: > > Hi all- > > As a way of introduction, I’m Ron, and I maintain Apple’s Swift > programming language package

Re: [CMake] CMake Project Generation Speedup

A round of performance improvements to generate time was done as part of CMake 3.11 and that significantly helped. What would be helpful is a performance analysis run of CMake itself to determine if the issue is that we are IO bound ( and need to do multi-threaded writes ) or compute bound. While

[CMake] [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

[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

[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:

[CMake] [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:

[CMake] [ANNOUNCE] CMake 3.14.0-rc3 is ready for testing

I am proud to announce the third 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 pending further development. Documentation is available at: https://cmake.org/cmake/help/v3.14

[cmake-developers] [ANNOUNCE] CMake 3.14.0-rc3 is ready for testing

I am proud to announce the third 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 pending further development. Documentation is available at: https://cmake.org/cmake/help/v3.14

Re: [CMake] CUDA language support with host compiler flags

Currently to get proper propagation of architecture flags such as -arch=sm_50, -compute=compute_X you need to place these into the CMAKE_CUDA_FLAGS. This is a known issue, as flags specified by `target_compile_options` are not propagate to the device linking step, which needs the correct

Re: [CMake] Getting the path to object files?

You can file an enhancement request that the $ generator expression to be relaxed to include STATIC, SHARED, and MODULE libraries. My suggestion is that a dummy source file to workaround the Xcode limitation on targets, is not as hacky as reverse engineering the object file locations. On Wed,

Re: [CMake] transitive interface dependency problem

If `interfaceDep` is an actual interface target, consuming libraries of libA inside the project ( example ) should resolve it as an interface target and not drop it on the lnik line. If you have a small self contained example that would help track down this issue. On Thu, Feb 21, 2019 at 5:49 AM

Re: [CMake] CUDA language support with host compiler flags

You need to guard the flags with `$` the evaluation on a given compiler id is done for all sources of a target, and not on each target source file. So you will need something like: set(cxx_flags "$<$,$>:-Wall -Wextra -pedantic> $<$:/W4")

Re: [CMake] Getting the path to object files?

CMake only provides an official way to get the location of the object files for OBJECT targets ( $ ). For other target types the location is an implementation detail. On Sat, Feb 23, 2019 at 3:24 PM Paul Smith wrote: > > Hi all. I'm using CMake 3.13.4 across Linux, MacOS, and Windows, with >

Re: [CMake] [SPAM] Re: [SPAM] Re: resource installation

I believe the problem is related to execute_process CODE not being quoted. So the following works for me: install(CODE " execute_process(COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/ResourceInstall.bat ${WIN_PLATFORM} ${CMAKE_BUILD_TYPE} RESULT_VARIABLE RI_RESULT

[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

[CMake] [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

Re: [CMake] Redundant linking when modifying shared libraries

I agree that we should document this property better. I recommend looking at the CMake wiki ( https://gitlab.kitware.com/cmake/community/wikis/home ) and thinking maybe adding a new recipe for `optimizing redundant linking`. On Thu, Feb 14, 2019 at 3:11 PM Itay Chamiel wrote: > > On Thu, Feb 14,

Re: [CMake] Redundant linking when modifying shared libraries

> I wonder why this isn't the default behavior By default CMake wants to get a correct build 100% of the time. There is nothing to stop people from having functions defined in a .cxx file with no corresponding header, and using manual forward deceleration is used in a consuming

Re: [CMake] [CMAKE] Disable testing when building using bootstrap

You can pass CMake arguments to the bootstrap by doing: ./bootstrap -- -DBUILD_TESTING=OFF On Mon, Feb 11, 2019 at 12:03 PM Jon Haitz Legarreta Gorroño wrote: > > Hi, > > I'm trying to build CMake from sources using the `bootstrap` script. > > Please, correct me if I'm wrong, but it looks like

[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

[CMake] [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

Re: [CMake] cmake with vscode

CMAKE_FIND_ROOT_PATH isn't meant to be used like that, you should use CMAKE_PREFIX_PATH I expect. ROOT_PATH represents the root of a new file-system/OS basically and is meant for cross-compilation. While what you want is extra directories to start searching from which is what CMAKE_PREFIX_PATH is

Re: [CMake] [SPAM] Re: resource installation

If you add 'OUTPUT_VARIABLE' and 'ERROR_VARIABLE' information to the execute_process call you should be able to dump the information using 'message' and see if the execute_process is running. On Tue, Jan 29, 2019 at 3:04 PM Rob Boehne wrote: > > I’m still not getting this script executed. I

Re: [CMake] [EXTERNAL] Re: Linking to boost on OS X 10.12

The version of the libraries that you load from your build directory would need to be fixed up to. On Tue, Feb 5, 2019 at 5:00 PM Stephens, J. Adam wrote: > > Hi Robert, > > Thanks for your reply. We do use install_name_tool and the like when > installing/packaging, and our packages continue to

Re: [CMake] Linking to boost on OS X 10.12

My general approach for the second problem is to run a tool such as install_name_tool to change the library names to have @rpath when constructing the package. On Tue, Feb 5, 2019 at 2:25 PM Stephens, J. Adam via CMake wrote: > > Hello, > > > > The project I work on links to several shared boost

Re: [CMake] patches for MirOS

As a general policy CMake doesn't offer patch releases of older versions, and instead recommends updating to the latest CMake version. On Sun, Feb 3, 2019 at 10:21 PM Andrew Pennebaker wrote: > > Hiya! > > I got cmake to build in MirOS (also known as MirBSD) v10 this weekend, > painting over

Re: [CMake] --warn-uninitialized works in only first configuration

Okay now I understand. Yes this is the intended behavior of `--warn-uninitialized`. It is designed so that it will only generate warnings for the explicit invocation of cmake that includes the flag. Subsequent calls to `cmake` without `--warn-uninitialized` will generate no warnings. On Tue,

Re: [CMake] --warn-uninitialized works in only first configuration

This generally occurs with CACHE variables as for non first runs they exist in the cache and therefore are initialized. On Mon, Feb 4, 2019 at 10:16 AM Ramold, Felix wrote: > > Hi, > > > > I configure a project with --warn-uninitialized and get a lot of warnings. I > successfully run the build.

[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

[CMake] [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

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

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

  1   2   >