Thanks Tyler,
I'll look into it. But it could very well be that I made a mistake in
one of my CMakeLists.txt (or CMake macro) files, since this happened
while I was developing those. At the moment I cannot reproduce the
error.
Best regards,
Marcel Loose.
On Thu, 2009-06-25 at 15:25 -0700, Tyler
On Thu, Jun 25, 2009 at 11:55:50PM +0200, Marcel Loose wrote:
> No, I'm not sure. I deduced that the command 'cmake -E copy ...' failed,
> because the file was not present in the destination directory, which (by
> the way) needed to be created. So maybe cmake does not return with an
> error status
No, I'm not sure. I deduced that the command 'cmake -E copy ...' failed,
because the file was not present in the destination directory, which (by
the way) needed to be created. So maybe cmake does not return with an
error status when the file copy fails?
Regards,
Marcel Loose.
On Thu, 2009-06-25
On Thu, Jun 25, 2009 at 11:39:41PM +0200, Marcel Loose wrote:
> However, if the command fails during make, I would assume that make
> would exit prematurely with an error status, but that didn't happen.
This is what I would expect as well. Are you sure that your command is
actually returning a non
Aah, of course. Didn't think hard enough about this problem.
However, if the command fails during make, I would assume that make
would exit prematurely with an error status, but that didn't happen.
Am I overlooking something?
Regards,
Marcel Loose.
On Thu, 2009-06-25 at 09:14 -0700, Tyler Rosco
On Thu, Jun 25, 2009 at 12:23:33PM +0200, Marcel Loose wrote:
> I have defined a custom command with add_custom_command(), and the
> command inside may fail.
>
> Is there a way to retrieve the error status of such a failing command,
> like with RESULT_VARIABLE in execute_process()?
Your custom_co
Hi all,
I have defined a custom command with add_custom_command(), and the
command inside may fail.
Is there a way to retrieve the error status of such a failing command,
like with RESULT_VARIABLE in execute_process()?
Best regards,
Marcel Loose.
___
