Thank you Nils, VERBATIM really worked for me as shown below:
*add_custom_command(*
* OUTPUT ${some_files}*
* COMMAND ${PYTHON_EXECUTABLE} test.py "" ${src} ${dst} *
* DEPENDS ${....... all deps ......}*
* VERBATIM )*
But now got a new question. I tried setting a variable and passing it, but
it didn't work. as shown below:
*set(prefix "")add_custom_command(*
* OUTPUT ${some_files}*
* COMMAND ${PYTHON_EXECUTABLE} test.py ${prefix} ${src} ${dst}*
* DEPENDS ${....... all deps ......} )*
Any idea why?
Abid K.
On Mon, Jun 30, 2014 at 1:35 PM, Nils Gladitz <[email protected]> wrote:
> On 06/30/2014 09:42 AM, abid rahman wrote:
>
>> Hello,
>>
>> I need to execute following command with add_custom_command:
>> *python test.py "" src dst*
>>
>>
>> The first argument is empty. Sometimes it may have some text. So Python
>> process the args as [test.py, "", src, dst]. But when I do the same with
>> add_custom_command, the empty argument is not considered, instead src is
>> considered as second argument.
>>
>> I did it as follows:
>>
>> *add_custom_command(
>> *
>> * OUTPUT ${some_files}
>> *
>> * COMMAND ${PYTHON_EXECUTABLE} test.py "" ${src} ${dst}
>> *
>> * DEPENDS ${....... all deps ......} )*
>>
>>
>> So what is the best method to pass empty arguments to cmake
>> add_custom_command?
>> Abid K.
>>
>
> Try adding VERBATIM.
>
> Nils
>
>
--
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:
http://public.kitware.com/mailman/listinfo/cmake
