Revision 52970dcaba0d1c00736f5319a97cb07acad3b1dd authored by Brad King on 08 June 2023, 14:44:19 UTC, committed by Kitware Robot on 08 June 2023, 14:44:38 UTC
e4c53cdc15 BinUtils: Drop now-unnecessary cross-compiling workaround for Apple hosts 1373373823 enable_language: Establish target platform identification variables earlier 1d916bf3d2 kFreeBSD,GNU: Provide multiarch library directory regex earlier Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Reviewed-by: Ben Boeckel <ben.boeckel@kitware.com> Merge-request: !8544
exec_program.rst
exec_program
------------
.. deprecated:: 3.0
Use the :command:`execute_process` command instead.
Run an executable program during the processing of the CMakeList.txt
file.
.. code-block:: cmake
exec_program(Executable [directory in which to run]
[ARGS <arguments to executable>]
[OUTPUT_VARIABLE <var>]
[RETURN_VALUE <var>])
The executable is run in the optionally specified directory. The
executable can include arguments if it is double quoted, but it is
better to use the optional ``ARGS`` argument to specify arguments to the
program. This is because cmake will then be able to escape spaces in
the executable path. An optional argument ``OUTPUT_VARIABLE`` specifies a
variable in which to store the output. To capture the return value of
the execution, provide a ``RETURN_VALUE``. If ``OUTPUT_VARIABLE`` is
specified, then no output will go to the stdout/stderr of the console
running cmake.
Computing file changes ...
