--- layout: fc_discuss_archives title: Message 16 from Frama-C-discuss on November 2013 ---
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] Frama-c - wp on Windows/Cygwin



Virgile, Pascal,

Getting rid of the link from a directory on the PATH did not help.
But putting the alt-ergo executable with that name directly in the 
working directory did work.
That is not the best organization, but will work for now.

- David

On 11/4/2013 3:05 AM, Virgile Prevosto wrote:
> Hello,
>
> 2013/11/3 David Cok <dcok at grammatech.com>:
>> Thanks, Pascal,
>>
>> Given your comments, I would expect that
>>> frama-c -wp swap.c
>> is closest to working, but can't find alt-ergo, even though it is on the
>> PATH.
>> Can you - or someone - comment on where wp expects alt-ergo (and under what
>> name)  on Windows?
> Pascal is right, this should work. I don't think WP expects alt-ergo
> to be anywhere (except on the PATH that is), but there might be subtle
> issues. In particular, you might encounter these symptoms if the
> alt-ergo file that is in your PATH is in fact a link to the real
> executable. You might also want to add the option -kernel-msg-key task
> to see which command is launched and which is its exit status.
>
> Best regards,