I found this little tidbit in the FAQ:
[E]nvironment variables SET in the CMakeLists.txt only take
effect for cmake itself, so you cannot use this method to set
an environment variable that a custom command might need.
I would like to augment the path during a custom command.
Is there a
Gregory C. Sharp wrote:
I found this little tidbit in the FAQ:
[E]nvironment variables SET in the CMakeLists.txt only take
effect for cmake itself, so you cannot use this method to set
an environment variable that a custom command might need.
I would like to augment the path during a
Bill Hoffman wrote:
Gregory C. Sharp wrote:
I found this little tidbit in the FAQ:
[E]nvironment variables SET in the CMakeLists.txt only take
effect for cmake itself, so you cannot use this method to set
an environment variable that a custom command might need.
I would like to augment
Gregory C. Sharp wrote:
Bill Hoffman wrote:
Gregory C. Sharp wrote:
I found this little tidbit in the FAQ:
[E]nvironment variables SET in the CMakeLists.txt only take
effect for cmake itself, so you cannot use this method to set
an environment variable that a custom command might need.
Make that cmake -P (not cmake -S) -S is the run this script arg to
ctest...
On Fri, Aug 15, 2008 at 11:45 AM, Bill Hoffman [EMAIL PROTECTED]wrote:
Gregory C. Sharp wrote:
Bill Hoffman wrote:
Gregory C. Sharp wrote:
I found this little tidbit in the FAQ:
[E]nvironment variables
David Cole wrote:
add_custom_command(OUTPUT output COMMAND ${CMAKE_COMMAND} -S
myscript.cmake)
myscript.cmake:
set(ENV{PATH} ...)
execute_process()
Make that cmake -P (not cmake -S) -S is the run this script arg to
ctest...
Works great. Thanks!
--
Gregory C.
