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: virgile.prevosto at cea.fr (Virgile Prevosto)
  • Date: Wed, 25 May 2011 17:38:32 +0200
  • In-reply-to: <569C6D7D26484241A530B87F45ADE1F87ABBE3@AOFRWMBXRSC004.resources.atosorigin.local>
  • References: <BANLkTimV1OtsBFc9aAf1a+rbp2bOzexQAQ@mail.gmail.com> <569C6D7D26484241A530B87F45ADE1F87ABBE3@AOFRWMBXRSC004.resources.atosorigin.local>
Hello,

Le mer. 25 mai 2011 15:30:54 CEST,
DUPRAT Stephane <STEPHANE.DUPRAT at atosorigin.com> a ?crit :

> 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
> 

This will work, but there's a one-step solution: use -cpp-command with
a string containing %1 and %2 as placeholders for the input file and
output file respectively. See section 5.1 of Frama-C's user manual,
http://frama-c.com/download/frama-c-user-manual.pdf
for more information and examples.

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