Alexander Neundorf wrote:
> EXECUTE_PROCESS(COMMAND ${RUBY_EXECUTABLE} -r rbconfig -e 'puts
> Config::CONFIG["libdir"]'
>OUTPUT_VARIABLE RUBY_POSSIBLE_LIB_PATH)
EXECUTE_PROCESS does not use a shell like EXEC_PROGRAM so it directly
converts CMake arguments into command line arguments. The abo
Hi,
please have a look at the attached CMakeLists.txt. There is one call to
EXEC_PROGRAM(), which works, and one call to EXECUTE_PROCESS(), where cmake
complains about an unterminate string.
I didn't find a way to get this working.
Did I just miss the right way or is it a bug ?
Alex
--
"Feel
Filipe Sousa wrote:
Now that cmake has EXECUTE_PROCESS command, should we use this instead
of EXEC_PROGRAM?
If you want. It is much more powerful. I'll add this to the documentation.
I notice that both commands captures output in a different way:
[snip]
EXECUTE_PROCESS does not remove the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Now that cmake has EXECUTE_PROCESS command, should we use this instead
of EXEC_PROGRAM?
I notice that both commands captures output in a different way:
EXEC_PROGRAM(${QT_QMAKE_EXECUTABLE}
ARGS -query QT_VERSION
OUTPUT_VARIABLE output1
RETU
