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] ReBuild the source file
- Subject: [Frama-c-discuss] ReBuild the source file
- From: tripathigaurav.gt at gmail.com (Gaurav Tripathi)
- Date: Thu, 4 Jun 2015 17:59:10 +0530
- In-reply-to: <1433420721279.1725785146@boxbe>
- References: <CAKi1EuhsjeUvOW8bwGH3iaQhJ7iQtjF65-zPYnWf4btfhR6BeA@mail.gmail.com> <1433420721279.1725785146@boxbe>
I am talking about Frama-c source file. What if I change frama-c source code ? On Thu, Jun 4, 2015 at 5:57 PM, Julien Signoles <Julien.Signoles at cea.fr> wrote: > [image: Boxbe] <https://www.boxbe.com/overview> This message is eligible > for Automatic Cleanup! (Julien.Signoles at cea.fr) Add cleanup rule > <https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Ftoken%3DFR7EFC6GkRDR7upuNa39GL2ICwWPYsnzrYYU7mtqvBY1AW5f%252FnVgCbu58YXmzvzpxvbEq7W8s2F2T0ijN0KBSBhrVjaaXFaXM5%252FrcC1SHKdLa9yMP%252FZfFWcHW2VEh2nqk7tU62XUAxOQs6uJBQcXBA%253D%253D%26key%3D1cb6nfGbiDoVBpzD1%252Bb%252B%252F7p5NNl5SPLGLclLTW9HJWk%253D&tc_serial=21545450351&tc_rand=595741085&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001> > | More info > <http://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=21545450351&tc_rand=595741085&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001> > > Hello, > > On 06/04/2015 02:16 PM, Gaurav Tripathi wrote: > >> If I modify the code and if I have to rebuild and create an executable, >> how can I do that? >> >> Is there any procedure given by Frama-C to rebuild my code and create >> executable ? >> >> What are the steps that are required to create an executable ? >> > > Frama-C is **not** a compiler. You can't generate an executable from this > tool. The standard way is to generate a new source code and then to use > your favorite C compiler to compile it as follow: > > $ frama-c <c files and options> -then -print -ocode generated.c > $ gcc <compilation options> generated.c > > Hope this helps, > Julien > -- > Researcher-engineer > CEA LIST, Software Security Labs > tel:(+33)1.69.08.00.18 fax:(+33)1.69.08.83.95 Julien.Signoles at cea.fr > _______________________________________________ > Frama-c-discuss mailing list > Frama-c-discuss at lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/frama-c-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20150604/8c28b326/attachment.html>
- Follow-Ups:
- [Frama-c-discuss] ReBuild the source file
- From: Julien.Signoles at cea.fr (Julien Signoles)
- [Frama-c-discuss] ReBuild the source file
- From: Andre.OLIVEIRAMARONEZE at cea.fr (Andre Oliveira)
- [Frama-c-discuss] ReBuild the source file
- From: abiao.yang at gmail.com (Yibiao)
- [Frama-c-discuss] ReBuild the source file
- References:
- [Frama-c-discuss] ReBuild the source file
- From: tripathigaurav.gt at gmail.com (Gaurav Tripathi)
- [Frama-c-discuss] ReBuild the source file
- Prev by Date: [Frama-c-discuss] ReBuild the source file
- Next by Date: [Frama-c-discuss] Journal File
- Previous by thread: [Frama-c-discuss] ReBuild the source file
- Next by thread: [Frama-c-discuss] ReBuild the source file
- Index(es):