[CMake] Cdash - Display Start Time in local time zone

2019-02-12 Thread Donald MacQueen [|] via CMake

Greetings,

I understand that start times are stored in UTC.

But I would like the Start Time column in the Dashboard window to 
display those times in my local time zone of 'America/New York' or EST.


I have looked at the code in index.php, but I am not a php expert.

2) Running date in Ubuntu gets this: Tue Feb 12 21:47:16 EST 2019

So why is the CDash browser showing the current time in UTC? Wednesday, 
February 13 2019 02:41:47.


I have my project nightly start time set to 00:00:01 EST.

Thanks in advance.

--
Donald [|]
A bad day in [] is better than a good day in {}.


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--

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] OBJECT libraries getting fully support?

2019-02-12 Thread Michael Ellery
https://cmake.org/cmake/help/latest/release/3.12.html says that 
target_link_libraries got OBJECT in 3.12 - is that what you had in mind?

-Mike

> On Feb 12, 2019, at 3:35 PM, Paul Smith  wrote:
> 
> Don't want to be a noodge but wondering if anyone has any thoughts
> about this question or ideas on how to solve my problem?
> 
> 
> On Sat, 2019-02-09 at 12:29 -0500, Paul Smith wrote:
>> Hi all;
>> 
>> I saw an email to the list from Chuck Atkins in the summer of 2017
>> suggesting that OBJECT libraries were being enhanced and could become
>> fully-functional libraries hopefully sometime that year.  I'm wondering
>> if that ever actally happened and if so what release of cmake it was
>> in, and if not is there still a plan for this sometime?
>> 
>> I'm trying to convert a large and complex cmake environment originally
>> started in 2007 or so, which uses all old-school cmake facilities, to
>> use modern cmake methods.
>> 
>> I have a situation where we have a library containing basic methods
>> which can be implemented multiple ways and different executables use
>> different implementations.  However these methods are used by all sorts
>> of static libraries as well.
>> 
>> Since we don't know until executable link time which library to use,
>> the static libraries cannot depend on the base library: it has to be
>> listed only in the executable's target_link_libraries.  But of course
>> because the static libraries use them as well we need the base library
>> to be listed last (or near last) in the link line else we get undefined
>> symbols.  Adding the base library to the executable TLL doesn't allow
>> us to do that.
>> 
>> So I was thinking of making this base library an OBJECT library so it
>> would always be fully linked but it seems that our version of cmake
>> doesn't allow an OBJECT library to be used as a normal library and I'd
>> be reduced to adding lots of generator expressions for it everywhere
>> which is a huge PITA.
>> 
>> Any ideas on how best to address this situation, if OBJECT libraries
>> are not supported yet?
> 
> -- 
> 
> 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] OBJECT libraries getting fully support?

2019-02-12 Thread Paul Smith
Don't want to be a noodge but wondering if anyone has any thoughts
about this question or ideas on how to solve my problem?


On Sat, 2019-02-09 at 12:29 -0500, Paul Smith wrote:
> Hi all;
> 
> I saw an email to the list from Chuck Atkins in the summer of 2017
> suggesting that OBJECT libraries were being enhanced and could become
> fully-functional libraries hopefully sometime that year.  I'm wondering
> if that ever actally happened and if so what release of cmake it was
> in, and if not is there still a plan for this sometime?
> 
> I'm trying to convert a large and complex cmake environment originally
> started in 2007 or so, which uses all old-school cmake facilities, to
> use modern cmake methods.
> 
> I have a situation where we have a library containing basic methods
> which can be implemented multiple ways and different executables use
> different implementations.  However these methods are used by all sorts
> of static libraries as well.
> 
> Since we don't know until executable link time which library to use,
> the static libraries cannot depend on the base library: it has to be
> listed only in the executable's target_link_libraries.  But of course
> because the static libraries use them as well we need the base library
> to be listed last (or near last) in the link line else we get undefined
> symbols.  Adding the base library to the executable TLL doesn't allow
> us to do that.
> 
> So I was thinking of making this base library an OBJECT library so it
> would always be fully linked but it seems that our version of cmake
> doesn't allow an OBJECT library to be used as a normal library and I'd
> be reduced to adding lots of generator expressions for it everywhere
> which is a huge PITA.
> 
> Any ideas on how best to address this situation, if OBJECT libraries
> are not supported yet?

-- 

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] [CMAKE] Disable testing when building using bootstrap

2019-02-12 Thread Jon Haitz Legarreta Gorroño
Hi Robert,
thanks. That answers the question !

Cheers,
JON HAITZ

On Tue, Feb 12, 2019 at 1:24 PM Robert Maynard
 wrote:
>
> 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 is being
> > built with `BUILD_TESTING=ON` by default.
> >
> > I'd like to disable testing (and any other non-essential option), but
> > AFAIK bootstrap does not expose the `-DBUILD_TESTING` flag, or I have
> > not found a way to set it to `OFF`.
> >
> > Is this possible / does this make sense at all? Can anyone please
> > provide me with the pointers to do so?
> >
> > Thank you,
> > JON HAITZ
> > --
> >
> > 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] link only with targets feature

2019-02-12 Thread Alexander Neundorf
On 2019 M02 12, Tue 08:02:43 CET Starka Tomáš wrote:
> tldr;
> It would be wonderful to have function or signature for
> target_link_libraries tha would link only to a targets. Did I overlook
> something?
> 
> like target_link_libraries(name [PUBLIC...] TARGETS myFavouriteLib ...
> QUIET/VERBOSE)
> 
...
> But then I guess it wouldn't hurt to have something like
> target_link_libraries(name [PUBLIC...] TARGETS myFavouriteLib ...
> QUIET/VERBOSE) which would not try to give linker myFavouriteLib.lib
> if there was no target of that name in question. Or
> target_link_targets... realy doesn't matter as long as it does that
> and maybe when asked by the last parameter it gives an error if the
> one of the target is non-existent or ill-formed. 

I agree to target_link_targets().
Additionally I would prefer if (maybe with a policy) include directories would 
be only applied when using target_link_targets(), but not when using 
target_link_libraries().
This would make it more obvious IMO.

Alex

-- 

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] [SPAM] Re: [SPAM] Re: resource installation

2019-02-12 Thread Rob Boehne
The same behavior is also present in version 3.14.0-rc1.

On 2/12/19, 11:54 AM, "CMake on behalf of Rob Boehne"  wrote:

Hmmm, I think I've found a bug.  Here is what I have in my top-level 
CMakeLists.txt file:


if(WIN32)
#
# run the script to install the resources
#
set(RI_RESULT " ")
set(RI_OUTPUT " ")
set(RI_ERROR " ")

install(CODE "message(\"running 
${CMAKE_CURRENT_SOURCE_DIR}/ResourceInstall.bat ${WIN_PLATFORM} 
${CMAKE_BUILD_TYPE}\")")

install(CODE execute_process(COMMAND 
${CMAKE_CURRENT_SOURCE_DIR}/ResourceInstall.bat ${WIN_PLATFORM} 
${CMAKE_BUILD_TYPE}
 RESULT_VARIABLE RI_RESULT
 OUTPUT_VARIABLE RI_OUTPUT
 ERROR_VARIABLE RI_ERROR
 OUTPUT_FILE ResInst.out
 ERROR_FILE ResInst.err )
   )

install(CODE "message(\"ResourceInstall results \\\"${RI_RESULT}\\\" 
output: \\\"${RI_OUTPUT}\\\"  error: \\\"${RI_ERROR}\\\" \")")

endif()


(As you can see I haven't figured out quoting yet)
This is what comes out of the above code:


if("x${CMAKE_INSTALL_COMPONENT}x" STREQUAL "xUnspecifiedx" OR NOT 
CMAKE_INSTALL_COMPONENT)
  message("running 
C:/Users/robb/Development/apdfl-sandbox/pdfl15_all/ResourceInstall.bat x64 
Release")
endif()

if("x${CMAKE_INSTALL_COMPONENT}x" STREQUAL "xUnspecifiedx" OR NOT 
CMAKE_INSTALL_COMPONENT)
  execute_process(COMMAND 
"C:/Users/robb/Development/apdfl-sandbox/pdfl15_all/ResourceInstall.bat x64 
Release"
WORKING_DIRECTORY C:/Users/robb/Development/apdfl-sandbox/pdfl15_all
RESULT_VARIABLE RI_RESULT
OUTPUT_VARIABLE RI_OUTPUT
ERROR_VARIABLE RI_ERROR
OUTPUT_FILE ResInst.out
ERROR_FILE ResInst.err ")
endif()

if("x${CMAKE_INSTALL_COMPONENT}x" STREQUAL "xUnspecifiedx" OR NOT 
CMAKE_INSTALL_COMPONENT)
  message("ResourceInstall results  output:   error:  ")
endif()


From cmake 3.12.2 on Win64.  The issue is the closing quote inside 
"execute_process"  which appears to have been magically added by cmake.
When I run the cmake_install.cmake as is it fails on that line:


CMake Error at cmake_install.cmake:87:
  Parse error.  Function missing ending ")".  Instead found unterminated
  string with text ")

  ".

If I remove that stray double quote, it runs, doing all the subdir install 
tasks, but still doesn't run the ResourceInstall.bat file.
And it generates the error:

1>  -- Installing: 
C:/Users/robb/Development/apdfl-sandbox/pdfl15_all/cmake_vs2013/../dist/x64/release/Resources/Sample_Input/XPStoPDF.xps
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: The command "setlocal
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: "C:\Program Files\CMake\bin\cmake.exe" -DBUILD_TYPE=RelWithDebInfo -P 
cmake_install.cmake
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: :cmEnd
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: :cmErrorLevel
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: exit /b %1
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: :cmDone
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: if %errorlevel% neq 0 goto :VCEnd
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: :VCEnd" exited with code -1.
1>Done executing task "Exec" -- FAILED.
1>Done building target "PostBuildEvent" in project "INSTALL.vcxproj" -- 
FAILED.
1>
1>Build FAILED.
1>
1>Time Elapsed 00:00:29.40
== Build: 0 succeeded, 1 failed, 31 up-to-date, 0 skipped ==


I know the batch file does not get run because I have statements at the top 
that create a file before anything else, and it also sends output to stdout.

Any advice on how I can move forward here?

Thanks,

Rob Boehne



On 2/5/19, 4:09 PM, "Robert Maynard"  wrote:

If you add 'OUTPUT_VARIABLE' and 'ERROR_VARIABLE' informat

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

2019-02-12 Thread Robert Maynard via CMake
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 is being
> built with `BUILD_TESTING=ON` by default.
>
> I'd like to disable testing (and any other non-essential option), but
> AFAIK bootstrap does not expose the `-DBUILD_TESTING` flag, or I have
> not found a way to set it to `OFF`.
>
> Is this possible / does this make sense at all? Can anyone please
> provide me with the pointers to do so?
>
> Thank you,
> JON HAITZ
> --
>
> 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] [SPAM] Re: resource installation

2019-02-12 Thread Rob Boehne
Hmmm, I think I've found a bug.  Here is what I have in my top-level 
CMakeLists.txt file:


if(WIN32)
#
# run the script to install the resources
#
set(RI_RESULT " ")
set(RI_OUTPUT " ")
set(RI_ERROR " ")

install(CODE "message(\"running 
${CMAKE_CURRENT_SOURCE_DIR}/ResourceInstall.bat ${WIN_PLATFORM} 
${CMAKE_BUILD_TYPE}\")")

install(CODE execute_process(COMMAND 
${CMAKE_CURRENT_SOURCE_DIR}/ResourceInstall.bat ${WIN_PLATFORM} 
${CMAKE_BUILD_TYPE}
 RESULT_VARIABLE RI_RESULT
 OUTPUT_VARIABLE RI_OUTPUT
 ERROR_VARIABLE RI_ERROR
 OUTPUT_FILE ResInst.out
 ERROR_FILE ResInst.err )
   )

install(CODE "message(\"ResourceInstall results \\\"${RI_RESULT}\\\" 
output: \\\"${RI_OUTPUT}\\\"  error: \\\"${RI_ERROR}\\\" \")")

endif()


(As you can see I haven't figured out quoting yet)
This is what comes out of the above code:


if("x${CMAKE_INSTALL_COMPONENT}x" STREQUAL "xUnspecifiedx" OR NOT 
CMAKE_INSTALL_COMPONENT)
  message("running 
C:/Users/robb/Development/apdfl-sandbox/pdfl15_all/ResourceInstall.bat x64 
Release")
endif()

if("x${CMAKE_INSTALL_COMPONENT}x" STREQUAL "xUnspecifiedx" OR NOT 
CMAKE_INSTALL_COMPONENT)
  execute_process(COMMAND 
"C:/Users/robb/Development/apdfl-sandbox/pdfl15_all/ResourceInstall.bat x64 
Release"
WORKING_DIRECTORY C:/Users/robb/Development/apdfl-sandbox/pdfl15_all
RESULT_VARIABLE RI_RESULT
OUTPUT_VARIABLE RI_OUTPUT
ERROR_VARIABLE RI_ERROR
OUTPUT_FILE ResInst.out
ERROR_FILE ResInst.err ")
endif()

if("x${CMAKE_INSTALL_COMPONENT}x" STREQUAL "xUnspecifiedx" OR NOT 
CMAKE_INSTALL_COMPONENT)
  message("ResourceInstall results  output:   error:  ")
endif()


From cmake 3.12.2 on Win64.  The issue is the closing quote inside 
"execute_process"  which appears to have been magically added by cmake.
When I run the cmake_install.cmake as is it fails on that line:


CMake Error at cmake_install.cmake:87:
  Parse error.  Function missing ending ")".  Instead found unterminated
  string with text ")

  ".

If I remove that stray double quote, it runs, doing all the subdir install 
tasks, but still doesn't run the ResourceInstall.bat file.
And it generates the error:

1>  -- Installing: 
C:/Users/robb/Development/apdfl-sandbox/pdfl15_all/cmake_vs2013/../dist/x64/release/Resources/Sample_Input/XPStoPDF.xps
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: The command "setlocal
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: "C:\Program Files\CMake\bin\cmake.exe" -DBUILD_TYPE=RelWithDebInfo -P 
cmake_install.cmake
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: :cmEnd
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: :cmErrorLevel
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: exit /b %1
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: :cmDone
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: if %errorlevel% neq 0 goto :VCEnd
1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(132,5): error 
MSB3073: :VCEnd" exited with code -1.
1>Done executing task "Exec" -- FAILED.
1>Done building target "PostBuildEvent" in project "INSTALL.vcxproj" -- FAILED.
1>
1>Build FAILED.
1>
1>Time Elapsed 00:00:29.40
== Build: 0 succeeded, 1 failed, 31 up-to-date, 0 skipped ==


I know the batch file does not get run because I have statements at the top 
that create a file before anything else, and it also sends output to stdout.

Any advice on how I can move forward here?

Thanks,

Rob Boehne



On 2/5/19, 4:09 PM, "Robert Maynard"  wrote:

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 can copy the “message” 
output and run it – and it does what I want, and I see it in 
cmake_install.cmake – the message() and execute_process() calls are inside of 
identical conditionals, but there’s no indication that it is executing,