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] analysing already preprocessed file

  • Subject: [Frama-c-discuss] analysing already preprocessed file
  • From: benjamin.monate at (Benjamin Monate)
  • Date: Wed, 25 May 2011 17:40:22 +0200
  • In-reply-to: <569C6D7D26484241A530B87F45ADE1F87ABBE3@AOFRWMBXRSC004.resources.atosorigin.local>
  • References: <569C6D7D26484241A530B87F45ADE1F87ABBE3@AOFRWMBXRSC004.resources.atosorigin.local>

Le 25/05/2011 17:30, DUPRAT Stephane a ?crit :
> Boris,
> Thanks for the tip, It works.
> A variant of the problem:
> Imagine I have a compiler that doesn't support the "-o" option (that exists).
> I guess a solution in 2 steps:
>    1/ preprocessing with my own compiler and producing a .i file
>    2/ analyse directly the .i file

3/ Read the user manual 5.2 p25
4/ run frama-c -kernel-help and read the inline documentation of the 
-cpp-command option
5/ Read the following paragraph from the inline help
-cpp-command <cmd>  <cmd> is used to build the preprocessing command.
                     Defaults to $CPP environment variable or else
		    "gcc -C -E -I.".
                     If unset, the command is built as follow:
                     CPP -o <preprocessed file> <source file>
                     %1 and %2 can be used into CPP string to mark the
                     position of <source file> and <preprocessed file>

Benjamin Monate