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: Tue, 3 Sep 2013 08:49:10 +0200
- In-reply-to: <CAA1cxuiRnanxWHJHhXFpRV9G3+pwnFbnNG9zQrCsx3PHQq+fdA@mail.gmail.com>
- References: <CAA1cxuiRnanxWHJHhXFpRV9G3+pwnFbnNG9zQrCsx3PHQq+fdA@mail.gmail.com>
2013/9/2 David Yang <abiao.yang at gmail.com>: > Right. So I used the Ocaml module named Unix to add the kernel file. > " > let in_channel = Unix.open_process_in "frama-c -print-share-path" in > let frama_c_share_path = Pervasives.input_line in_channel in > let filename = frama_c_share_path ^ "/libc/fc_runtime.c" in Inside a Frama-C script/plug-in, you don't need to do that: the information is directly accessible in the Config.datadir value (see src/kernel/config.mli for the list of configuration variables that are available). Best regards, -- E tutto per oggi, a la prossima volta Virgile
- References:
- [Frama-c-discuss] How to use the frama-c builtins programmatically?
- From: abiao.yang at gmail.com (David Yang)
- [Frama-c-discuss] How to use the frama-c builtins programmatically?
- Prev by Date: [Frama-c-discuss] How to use the frama-c builtins programmatically?
- Next by Date: [Frama-c-discuss] JFLA 2014 - Troisieme appel a Communication
- Previous by thread: [Frama-c-discuss] How to use the frama-c builtins programmatically?
- Next by thread: [Frama-c-discuss] How to use the frama-c builtins programmatically?
- Index(es):