[Cmake-commits] CMake branch, master, updated. v3.15.0-rc2-109-g512013e

2019-06-20 Thread Kitware Robot
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 39d6e36..ad0386e 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 15) -set(CMake_VERSION_PATCH 20190620) +set(CMake_VER

Re: [CMake] Make Timeout not be a failure

2019-06-20 Thread Kyle Edwards
On Thu, 2019-06-20 at 16:47 -0400, Donald MacQueen [|] wrote: > HI Kyle, > > Where are the -D and the -P switches of add_test documented? Those are not part of add_test(), they are arguments that get passed to the CMake executable. See for details:

Re: [CMake] Make Timeout not be a failure

2019-06-20 Thread Donald MacQueen [|] via CMake
HI Kyle, Where are the -D and the -P switches of add_test documented? Thanks for the suggestion. On 6/20/2019 3:52 PM, Kyle Edwards wrote: On Thu, 2019-06-20 at 15:45 -0400, Donald MacQueen [|] via CMake wrote: I have a test where I start a program that I know will create some output that I

Re: [CMake] Make Timeout not be a failure

2019-06-20 Thread Kyle Edwards
On Thu, 2019-06-20 at 15:45 -0400, Donald MacQueen [|] via CMake wrote: > I have a test where I start a program that I know will create some  > output that I can test. > > But I have no way to kill this program, so I let Ctest kill it with > a  > TIMEOUT. > > The next step greps the output to

[CMake] Make Timeout not be a failure

2019-06-20 Thread Donald MacQueen [|] via CMake
I have a test where I start a program that I know will create some output that I can test. But I have no way to kill this program, so I let Ctest kill it with a TIMEOUT. The next step greps the output to see if it worked. So it would be nice if  PASS_REGULAR_EXPRESSION  could override

Re: [CMake] How to specify Redhat Developer Toolset compiler?

2019-06-20 Thread Jim Melton
I fought with this and ended up with the below approach. Note that these values are cached, so you must start with a clean build directory before changing. Assuming your desired versions are on your path: CC=$(which gcc) CXX=$(which g++) cmake3 --- Jim Melton Principal Software Engineer

Re: [CMake] How to specify Redhat Developer Toolset compiler?

2019-06-20 Thread Scott Bloom
We have a similar issue at my company, so the call to /opt/rh/devtoolset-X/enable is done in our bashrc files Then we use CMAKE__COMPILER_VERSION in our cmake file to make sure its set correctly. Scott From: CMake On Behalf Of David Aldrich Sent: Thursday, June 20, 2019 8:40 AM To: CMake

Re: [CMake] How to specify Redhat Developer Toolset compiler?

2019-06-20 Thread Eric Noulard
I would bet that enabling the toolset before launching CMake will do the trick. Otherwise set CC and/or CXX env var to the desired path before launching CMake. Le jeu. 20 juin 2019 à 17:39, David Aldrich a écrit : > My Centos 7.6 machine has CMake 3.13.5 and g++ 4.8.5 installed: > > $

Re: [CMake] How to specify Redhat Developer Toolset compiler?

2019-06-20 Thread Andreas Naumann
You could set the environment variables CXX and CC such that they point to your toolset compiler Am 20.06.19 um 17:39 schrieb David Aldrich: My Centos 7.6 machine has CMake 3.13.5 and g++ 4.8.5 installed: $ /usr/bin/x86_64-redhat-linux-g++ --version x86_64-redhat-linux-g++ (GCC) 4.8.5 20150623

[Cmake-commits] CMake branch, master, updated. v3.15.0-rc2-108-gcecf7e6

2019-06-20 Thread Kitware Robot
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via cecf7e61c4816e4a3bb55df243c6bf84f6df6e58 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.15.0-rc2-4-g036752c

2019-06-20 Thread Kitware Robot
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 036752cc0e5f98a611c23c044e3bc1b484b02f53 (commit) via

[CMake] How to specify Redhat Developer Toolset compiler?

2019-06-20 Thread David Aldrich
My Centos 7.6 machine has CMake 3.13.5 and g++ 4.8.5 installed: $ /usr/bin/x86_64-redhat-linux-g++ --version x86_64-redhat-linux-g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36) I have a very simple CMakeLists.txt: cmake_minimum_required(VERSION 3.5 FATAL_ERROR) project(hello_world LANGUAGES CXX)

[Cmake-commits] CMake branch, master, updated. v3.15.0-rc2-96-g282fa97

2019-06-20 Thread Kitware Robot
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 282fa97a45f19356260e73dbe26ae4b1d2501a07 (commit) via

Re: [CMake] ExternalProjectAdd and patch on Windows

2019-06-20 Thread Cristian Adam
Hi, If the users have git installed, you could try find_program(git...), and then "git apply", which should work to apply patches. Cheers, Cristian. On Thu, Jun 20, 2019 at 1:21 PM Kris Thielemans wrote: > Hi all > > > > I have a superbuild project where I need to patch a library (HDF5) after

[CMake] ExternalProjectAdd and patch on Windows

2019-06-20 Thread Kris Thielemans
Hi all I have a superbuild project where I need to patch a library (HDF5) after download. In Windows, there's no "patch" or "sed" command, and this has to run on other people's computer. I can almost achieve what I want in Powershell like so get-content ConfigureChecks.cmake | %{$_

Re: [CMake] CMake Digest, Vol 182, Issue 32

2019-06-20 Thread Michael Wild
On Wed, Jun 19, 2019 at 11:30 AM Innokentiy Alaytsev wrote: > Hello! > > Are the header files of the shared library (DLL) listed as INTERFACE_SOURCES > for the library target? AFAIK, the only reason for header files to be > processed by AUTOMOC is to be part of the project. The only way that I