Note: these instructions refer to an older release of Frama-C; for the latest stable release, click here

Mac OS X Leopard installation for Frama-C Lithium (released on 2008-12-01)

You need to be familiar with Unix to make use of this binary distribution. Frama-C is not at this time packaged as an application bundle. Mac OS X 10.5 (Leopard) is required. The binaries are known not to work on Mac OS X 10.4 (Tiger).

From the README:

This is the binary release of Frama-C for Mac OS X. It contains libraries which are provided as binaries as a convenience only. These libraries are covered by their respective licenses. The SVN repository of MacPorts of Dec 10, 2008 should be considered as the reference for this list of libraries. The MacPorts SVN repository contains links to their source code, for those libraries which make this a condition to re-distribution.

In addition to libraries from MacPorts, this package contains APRON 0.9.9 and alt-ergo 0.8.

Please untar the archive as root in /
It will not work from another location. You should probably install the included DejaVu fonts (see the first bug in the following list). You should also put the directory /usr/local/Frama-C/bin in your path.
Once all this is done, you are set up.

To play the tutorial, type:

frama-c-gui \
       -general-font "DejaVu Sans" \
       -monospace-font "DejaVu Sans Mono" \
       -slevel 10 first.c

Some known bugs specific to this binary distribution:

  • The display of unicode characters is broken with the default settings. A workaround is to install the "DejaVu Sans" and "DejaVu Sans Mono" fonts provided in the folder /usr/local/Frama-C/lib/dejavu_fonts, and always to use the command-line options:
    frama-c-gui \
           -general-font "DejaVu Sans" \
           -monospace-font "DejaVu Sans Mono" ...
    To install the fonts, open the files "DejaVuSans.ttf" and "DejaVuSansMono.ttf" and click the button "Install font" that appears in the Font Book dialog.
    Note: this workaround shouldn't be necessary. When it is used by the system (as opposed to pango), the Monaco font (for instance) falls back to another more complete font for the unicode characters that are missing. If someone knows how to fix this (probably in the fontconfig files), please contact me.
  • When creating a project from within the GUI, empty lines in the source code panels are displayed wrong, causing line numbers to overlap. Again, if someone knows how to fix this, please contact me.
  • The package should include a Mac OS X-ish theme, to make appearance, keybindings, ... closer to a native Mac OS X application.