[CMake] Re: TRY_COMPILE painful for tool testing

[Brad King]

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?

-Brad