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] Standalone application

  • Subject: [Frama-c-discuss] Standalone application
  • From: vanush at gmail.com (Vanush Vaswani)
  • Date: Mon, 29 Dec 2014 11:19:38 +1100
  • In-reply-to: <CA+yPOVhX4vusS9+=vQEa6+k9ofRORE1WBfKMx463GyJ8THqHCw@mail.gmail.com>
  • References: <CAJbabrijYBwNrrZUeAHbgUTVQDqi_DeR0h-6GTXye21cLf1S8A@mail.gmail.com> <CA+yPOVhX4vusS9+=vQEa6+k9ofRORE1WBfKMx463GyJ8THqHCw@mail.gmail.com>
Thanks.. 35Mb executable ;)
Anyway I could get a dynamically linked executable and get end-users
to copy the frama-c libs?

On Wed, Dec 24, 2014 at 8:03 PM, Virgile Prevosto
<virgile.prevosto at m4x.org> wrote:
> Hello,
>
> 2014-12-23 1:03 GMT+01:00 Vanush Vaswani <vanush at gmail.com>:
>> Is it possible to write a plugin and have it link to Frama-C in a
>> standalone executable? If so, are there any example of the Makefile?
>>
> Do you mean statically link the plugin to obtain a new executable? If
> so, and if you're including Makefile.dynamic as suggested by the
> manual, 'make static' should achieve what you want (note however that
> this is not the most tested way of compiling a Frama-C plugin).
>
> Best regards,
> --
> E tutto per oggi, a la prossima volta
> Virgile
> _______________________________________________
> 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