Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] Windows Install

  • Subject: [Frama-c-discuss] Windows Install
  • From: Pascal.CUOQ at (CUOQ Pascal)
  • Date: Fri, 2 Oct 2009 21:10:33 +0200
  • References: <000c01ca438e$7134c060$539e4120$@com>


this is intended to complement Benjamin's answer.

> Anyways, I am
> having some simple startup configuration problems in starting up Frama-C and
> trying out the example "first.c" as shown on the website. I see there are
> ample instructions for installing on Linux, but has anyone written down
> instructions and dependencies for a Windows installation? 

The instructions may seem to occupy more space for Linux, but
it's only because it is more difficult to install Frama-C on Linux :)
Windows is 100% supported, and some of our existing industrial
partners use it (I think) exclusively.

> In particular, when I run the following example command line I get the
> following errors:
> C:\Frama-C>frama-c-gui -slevel 10 -val first.c
> 'gcc' is not recognized as an internal or external command,
> operable program or batch file.

It seems that if you want to run the example without having to
dig into the manual, you must have GCC installed under the name
gcc and in your path.

If this condition is true in your environment, the error message is
very strange and we will need to study it further.
If the condition is false, could you suggest
a better default pre-processing command for Windows,
a command that Frama-C's Windows version could try
when this one fails?

To make it work now without fixing Frama-C, the workarounds
suggested by Benjamin are your best options. I fixed a couple
of grammar issues today in the manual he linked to. The
changes will take a short while to propagate to the web site,
but anyway, I'm always glad to have my mistakes pointed to me
by a native speaker.