[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

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 pref

[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

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

[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

: 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

[CMake] [ANNOUNCE] CMake 3.16.3 available for download

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

Re: [CMake] [ANNOUNCE] CMake Discourse forum now available

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 com

[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

PATH 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

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

t; 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 > > -

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

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

[CMake] [ANNOUNCE] CMake 3.15.3 available for download

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

Re: [CMake] How to specify VS2017 compilers when on VS2019

You can use that method so you get the IDE features of VS2019 but the VS2017 compiler. On Fri, Aug 16, 2019 at 2:19 PM Michael Jackson wrote: > > Why can't I do -T v141? > > -- > Mike Jackson > > On 8/16/19, 2:09 PM, "Kyle Edwards" wrote: > > On Fri, 2019-08-16 at 13:54 -0400, Michael

Re: [CMake] Ways to require CUDA arch minimum version?

Are you asking for a minimum CUDA SDK version or a restriction based on the hardware of the machine? We have no pre-built logic to enforce a minimum hardware component, as we want to support building CUDA on a machine without a GPU. As far as minimum CUDA SDK is concerned if you are doing it

[CMake] [ANNOUNCE] CMake 3.15.2 available for download

We are pleased to announce that CMake 3.15.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.15.2 since 3.15.1:

[cmake-developers] [ANNOUNCE] CMake 3.15.2 available for download

We are pleased to announce that CMake 3.15.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.15.2 since 3.15.1:

[cmake-developers] [ANNOUNCE] CMake 3.15.1 available for download

es Marc Chevrier (1): FindPython: ensure interpreter is founded when cross-compiling Marek Antoniak (1): Fix allocation in CROSSCOMPILING_EMULATOR evaluation Robert Maynard (2): FindMPI: Updated to use INTERFACE_LINK_OPTIONS FindMPI: make sure computed link flags are not de-duplicated Saleem Abdulr

[CMake] [ANNOUNCE] CMake 3.15.1 available for download

es Marc Chevrier (1): FindPython: ensure interpreter is founded when cross-compiling Marek Antoniak (1): Fix allocation in CROSSCOMPILING_EMULATOR evaluation Robert Maynard (2): FindMPI: Updated to use INTERFACE_LINK_OPTIONS FindMPI: make sure computed link flags are not de-duplicated Saleem Abdulr

Re: [CMake] Shortcomings with exporting and importing targets

ckages` to include to my > `*-config.cmake`?? > > On Thu, Jul 25, 2019 at 5:49 PM Robert Maynard > wrote: >> >> target_link_libraries() when given an explicit path+filename as PUBLIC >> ( not PRIVATE ) will be part of the transitive dependencies. An >> exp

Re: [CMake] Shortcomings with exporting and importing targets

target_link_libraries() when given an explicit path+filename as PUBLIC ( not PRIVATE ) will be part of the transitive dependencies. An explicit path+filename is not a target to CMake, nor will CMake compute that it maps to an existing target ( be it imported or a 'normal' target ). > This makes

Re: [CMake] add_subdirectory namespaces

Subsequent calls to project() from sub-directories is supported. For calls to project from sub-directories it does everything but set CMAKE_PROJECT_NAME. On Wed, Jul 24, 2019 at 7:29 AM Jason Beach wrote: > > I've been reorganizing / updating our software cmake build. It currently uses > a

Re: [CMake] getting compiler's include paths

as by product. On Wed, Jul 3, 2019 at 10:51 AM Robert Maynard wrote: > > I completely forgot that the Makefiles based generators in CMake have > a separate heuristic for determining system headers. > > If you use the Ninja generator I see the expected behavior: > ~/W/t/nbuild $ sudo touch

Re: [CMake] relative path to toolchain does not work

Is this with a clean build directory? The toolchain file is ignored once CMake has run and has done compiler detection. On Wed, Jul 17, 2019 at 11:29 AM hex wrote: > > I specified my toolchain like so: > > 1cmake -DCMAKE_TOOLCHAIN_FILE=myToolchain.cmake .. > > and created a toolchain file in

[cmake-developers] [ANNOUNCE] CMake 3.15.0 available for download

I am happy to announce that CMake 3.15.0 is now available for download at: 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

[CMake] [ANNOUNCE] CMake 3.15.0 available for download

I am happy to announce that CMake 3.15.0 is now available for download at: 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

[cmake-developers] [ANNOUNCE] CMake 3.14.6 available for download

We are pleased to announce that CMake 3.14.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.14.6 since 3.14.5:

[CMake] [ANNOUNCE] CMake 3.14.6 available for download

We are pleased to announce that CMake 3.14.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.14.6 since 3.14.5:

[cmake-developers] [ANNOUNCE] CMake 3.15.0-rc4 is ready for testing

instead. * The "ADDITIONAL_MAKE_CLEAN_FILES" directory property is now deprecated. Use the "ADDITIONAL_CLEAN_FILES" directory property instead. * The variable "CMAKE_AUTOMOC_RELAXED_MODE" is considered deprecated. Support still exists but will be removed in future versions.

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

instead. * The "ADDITIONAL_MAKE_CLEAN_FILES" directory property is now deprecated. Use the "ADDITIONAL_CLEAN_FILES" directory property instead. * The variable "CMAKE_AUTOMOC_RELAXED_MODE" is considered deprecated. Support still exists but will be removed in future versions.

Re: [CMake] getting compiler's include paths

jl forums wrote: > > ok, thanks > by the way what about my ctags rule? how can i get the include path of an > app? so that i can pass it to ctags and have my tags produced? > thanks and regards > jlm > > Le mer. 3 juil. 2019 à 16:52, Robert Maynard a > écrit

Re: [CMake] getting compiler's include paths

/usr/include/c++/8/istream /usr/include/c++/8/ios \ > /usr/include/c++/8/bits/basic_ios.h \ > /usr/include/c++/8/bits/basic_ios.tcc /usr/include/c++/8/ostream \ > /usr/include/c++/8/bits/ostream.tcc /usr/include/c++/8/bits/istream.tcc \ > /usr/include/x86_64-linux-gnu/c++/8/bits

Re: [CMake] compiling .cpp/.cxx with CUDA compiler

In general I go with the source property approach, since you can pass it a collection of files to be marked as CUDA. If you are aware of when all sources have been added to a target you can easily mark them all as cuda with: get_target_property(source_files SOURCES)

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

I am proud to announce the third 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-rc3 is ready for testing

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

Re: [CMake] getting compiler's include paths

It look that starting with CMake 3.6 modification of system headers will cause CMake to recompile projects. What version of CMake and your compiler are you using? On Mon, Jun 17, 2019 at 9:40 AM jl forums wrote: > > Hi, > I want to create a full tag file and for this require to know the compiler

[cmake-developers] [ANNOUNCE] CMake 3.15.0-rc2 is ready for testing

"export(PACKAGE)" command now does nothing unless enabled via "CMAKE_EXPORT_PACKAGE_REGISTRY". See policy "CMP0090". * The "Xcode" generator now requires at least Xcode 5. * An explicit deprecation diagnostic was added for policy "CMP0066"

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

"export(PACKAGE)" command now does nothing unless enabled via "CMAKE_EXPORT_PACKAGE_REGISTRY". See policy "CMP0090". * The "Xcode" generator now requires at least Xcode 5. * An explicit deprecation diagnostic was added for policy "CMP0066"

Re: [CMake] How to specify debug version of CRT library for Visual Studio generator?

Just a heads up, CMake 3.15 is introducing policy 91 which removes the runtime library from the default set of flags, and instead has targets establish what runtime they want. For more information see: https://cmake.org/cmake/help/v3.15/prop_tgt/MSVC_RUNTIME_LIBRARY.html On Tue, Jun 18, 2019 at

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

see: https://github.com/Kitware/CMake/blob/master/Modules/UseJava.cmake > > I'm not developing with golang but AFAIK go has a builtin "build system" so > bringing go as a language in CMake may not be the best option, > but again I am no Go expert. > > The only reference of

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

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: Thursday, May 9, 2019 3:12 > To: Zehner　Paul > Cc: Kai

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

pan > > 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 > Subjec

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

; Thx! > > On Tue, Apr 16, 2019 at 1:10 PM Robert Maynard > wrote: >> >> 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 expl

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:

  1   2   3   4   5   6   7   8   >