[CMake] Calling a Python Testing Script from CMake/CTest

Hi, I am having difficulty getting a python script to run a C++ subprocess on Window 7 using VS2013. On Linux, the following code works fine, but on Windows, from the command line I get the following output: Microsoft (R) Program Maintenance Utility Version 12.00.21005.1 Copyright (C) Microsoft C

Re: [CMake] Calling a Python Testing Script from CMake/CTest

Am 24. Februar 2016 15:09:47 MEZ, schrieb George Ryan : >Hi, > >I am having difficulty getting a python script to run a C++ subprocess >on Window 7 using VS2013. On Linux, the following code works fine, but >on Windows, from the command line I get the following output: > >Microsoft (R) Program M

Re: [CMake] Calling a Python Testing Script from CMake/CTest

Am 24. Februar 2016 15:09:47 MEZ, schrieb George Ryan : >> Hi, >> >> I am having difficulty getting a python script to run a C++ subprocess >> on Window 7 using VS2013. On Linux, the following code works fine, but >> on Windows, from the command line I get the following output: >> >> Microsoft (R)

Re: [CMake] Calling a Python Testing Script from CMake/CTest

My guess is that the command prompt is seeing the .py extension and automatically invoking the python interpreter for you. On other platforms it looks for the #!/usr/bin/env python which won’t work on windows.What you should do is use the FindPythonInterp cmake module to find your python executa

Re: [CMake] Calling a Python Testing Script from CMake/CTest

Thanks, Matthew. That worked. I had tried something similar using find(PythonInterp REQUIRED), but that didn't work. The include() worked perfectly! Thanks! George On 02/24/2016 10:51 AM, Matthew Keeler wrote: My guess is that the command prompt is seeing the .py extension and automatically i

Re: [CMake] [ANNOUNCE] CMake 3.5.0-rc3 is now ready!

Hello, I discovered that the Visual Studio 2015 Generator does not work with v120 toolsets (#15986) and consider that major issue. As far as I see this is related to the debug information setting from #15894. Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and c

[CMake] Immutable variables?

I ran across a project that set CMAKE_SOURCE_DIR/CMAKE_BINARY_DIR. This is a really bad idea, but apparently used to work for their use case. With cmake 3.5 this no longer works, but was somewhat hard to track down. I'm wondering if is makes to be able to mark cmake generated variables as immuta

Re: [CMake] Calling a Python Testing Script from CMake/CTest

It actually should be used using find_package() HS Am 24. Februar 2016 16:10:49 MEZ, schrieb George Ryan : >Thanks, Matthew. That worked. > >I had tried something similar using find(PythonInterp REQUIRED), but >that didn't work. The include() worked perfectly! > >Thanks! >George > > >On 02/24/2