Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • stable/zinc
  • 2699-wp-region-plugin-division-by-0-with-empty-region-node
  • stable/copper
  • stable/nickel
  • stable/cobalt
  • stable/iron
  • stable/manganese
  • stable/chromium
  • stable/vanadium
  • stable/titanium-backport
  • stable/titanium
  • stable/scandium
  • 30.0 protected
  • 30.0-beta protected
  • MIEL-2024-10 protected
  • 29.0 protected
  • 29.0-beta protected
  • 28.1 protected
  • 28.0 protected
  • MIEL-2023-10 protected
  • 28.0-beta protected
  • 27.1 protected
  • 27.0 protected
  • 27.0-beta protected
  • 26.1 protected
  • 26.0 protected
  • 26.0-beta protected
  • 25.0-r1 protected
  • pre-dune protected
  • 25.0 protected
  • 25.0-beta protected
  • 2022-03-23 protected
33 results
Compare
user avatar
[devguide] ensures we compile tutorial examples with current Frama-C
Virgile Prevosto authored 
Having relative directories in the PATH is rarely a good idea.
Moreover, if the PATH is set as part of the sub-make command, it does
not seem to always be given to the `$(shell ...)` command. It is thus more
robust to set it explicitely _before_ launching the sub-`$(MAKE)`
8e99e61e
History
user avatar 8e99e61e
History
Name Last commit Last update
..
check_api
examples
hello_world
tutorial
.gitignore
METADOC.txt
Makefile
Makefile.config
README
TODO
advance.tex
architecture.tex
changes.tex
developer.bib
developer.tex
dynamic.fig
framed.sty
introduction.tex
macros.sty
mecanism.fig
mecanism.pdf
overview.fig
refman.tex
tutorial.tex
README
Makefile.config:

It contains references to the external programs used to compile the
developer documentation.

Instead of fig2pdf some might want to use fig2dev (part of the xfig
package).
Use "figdev -L pdf" instead of for the FIG2PDF macros in this case.