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] configure: gui: no (see warning about /usr/local/lib/ocaml/lablgtk2/lablgtksourceview.cma, /usr/local/lib/ocaml/lablgtksourceview/lablgtksourceview.cma)

Am 31.03.2010 um 18:31 schrieb aintest3f aintest3l:

> yeah, I was really looking forward to these great and wonderful features I've read about too and what you mention below, but it's no good if it's so difficult to get it up and running. I might have missed it but I don't recall seeing and reporting feature from frama-c. Having great complex sophisticated analysis is absolutely fantastic but without properly representing the analyzed data to the users...
> 
> Please don't take me wrong, Frama-C is probably great, i'm just providing my feedback and my experience as a first time user...
> 
> Anyways, I was trying to recall why i didn't just go with the OSX binary in the first place, thanks for reminding me, that's because gcc is required and I can't get gcc binary for OSX.
> 

I must say that for someone who does not know how to install gcc on OSX (see the xcode package
on your install Mac OS X DVD!) you come across rather demanding!

The Frama-C OSX binary package works in my experience quite well (I am using it for the Jessie plugin).

Regards Jens