[CMake] Re: TRY_COMPILE painful for tool testing

[Brandon J. Van Every]

Brad King wrote:
> Brandon J. Van Every wrote:
>   
>> I think the result is, quotes and backslashes cannot be reliably escaped
>> with respect to macro wrappers for ADD_CUSTOM_TARGET.  Thus it is not
>> possible to write a macro that will TRY_COMPILE an arbitrary COMMAND.
>>
>> So the feature that I would like, is a TRY_COMMAND that produces, in the
>> native shell, whatever you actually give it for command arguments.  The
>> interface should be:
>>
>>   TRY_COMMAND(RESULT_VAR <arbitrary commands with quotes, backslashes,
>> semicolons, and whitespace>)
>>     
>
> What is an example command you want to test that is having problems?
>   

${DARCS_NATIVE_EXE} changes --repodir=${CHICKEN_NATIVE_DIR} > ChangeLog


MSVC, Cygwin, and MSYS all have different path behavior.  What is 
actually needed on both MSVC and MSYS is:

"E:\Program Files\darcsdir-w32\darcs.exe" changes 
--repodir="E:\devel\src\chicken" > ChangeLog


Cheers,
Brandon Van Every

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/cmake/attachments/20060920/94aa5db1/attachment.html