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] Can I change the compiler gcc into sdcc for frama-c and how?

Hello,

Le ven. 8 mars 2019 à 09:06, newbieroc <newbieroc at 163.com> a écrit :

> Hi,
>   I've used the slicer of frama-c; it's very useful to analyze C code
> actually. But, when I try to analyze the embedded codes, I even couldn't
> import the files.
> It's not compatible with it, I think, though I preprocess the codes with
> sdcc.
>   So, I have a doubt whether I can change the compiler gcc into sdcc so
> that I can analyze the embedded codes well. If can, how to do it?
>
>
As mentioned in the user manual (
http://frama-c.com/download/user-manual-18.0-Argon.pdf, chapter 5 -
Preparing the Sources), you can use option -cpp-command to control which
program is responsible for pre-processing the files, and/or -cpp-extra-args
to pass specific options to the pre-processor.
In addition note that by default Frama-C will use its own version of
standard libc headers. If your implementation uses specific headers that
are not compatible with that, you might try to use -no-frama-c-stdlib.

Best regards,
-- 
E tutto per oggi, a la prossima volta
Virgile
-------------- section suivante --------------
Une pièce jointe HTML a été nettoyée...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20190308/ca0ee124/attachment.html>