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] How to use the frama-c builtins programmatically?

  • Subject: [Frama-c-discuss] How to use the frama-c builtins programmatically?
  • From: virgile.prevosto at m4x.org (Virgile Prevosto)
  • Date: Mon, 2 Sep 2013 15:05:10 +0200
  • In-reply-to: <52247DD9.3080407@gmail.com>
  • References: <mailman.4956.1378112165.1217.frama-c-discuss@lists.gforge.inria.fr> <52247DD9.3080407@gmail.com>
2013/9/2 David <abiao.yang at gmail.com>:

> I am trying to treat those C functions in fc_runtime.c to be analyzed.
> I can ahieve this by codeing like this:
>
> Kernel.Files.add "/usr/local/share/frama-c/libc/fc_runtime.c";
>

Yes, then it's the best way to achieve what you want. For portability,
if you use your script on different machines where Frama-C might not
always be installed on /usr/local, you can use something like
(Config.datadir ^ "/libc/fc_runtime.c"), but it really depends on your
configuration.

Best regards,
-- 
E tutto per oggi, a la prossima volta
Virgile