From 93c116570591ac32bb6d19ee3fc23b9abd348a78 Mon Sep 17 00:00:00 2001 From: Brad King Date: Mon, 8 Jul 2013 11:35:56 -0400 Subject: [PATCH] ExternalProject: Document multiple COMMAND lines We support multiple commands per external project step by using the COMMAND keyword. Document this behavior and show an example. While at it, document that shell operators and current working directory behavior is not defined. --- Modules/ExternalProject.cmake | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Modules/ExternalProject.cmake b/Modules/ExternalProject.cmake index 6afdb9735..3acb4f91f 100644 --- a/Modules/ExternalProject.cmake +++ b/Modules/ExternalProject.cmake @@ -114,6 +114,15 @@ # and # with corresponding property values. # +# Any builtin step that specifies a "_COMMAND cmd..." or custom +# step that specifies a "COMMAND cmd..." may specify additional command +# lines using the form "COMMAND cmd...". At build time the commands will +# be executed in order and aborted if any one fails. For example: +# ... BUILD_COMMAND make COMMAND echo done ... +# specifies to run "make" and then "echo done" during the build step. +# Whether the current working directory is preserved between commands +# is not defined. Behavior of shell operators like "&&" is not defined. +# # The 'ExternalProject_Get_Property' function retrieves external project # target properties: # ExternalProject_Get_Property( [prop1 [prop2 [...]]])