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] Dynamic Plugin Enabled in Linux but Failed in Windows

  • Subject: [Frama-c-discuss] Dynamic Plugin Enabled in Linux but Failed in Windows
  • From: Julien.Signoles at (Julien Signoles)
  • Date: Thu, 26 Jul 2012 15:21:18 +0200
  • In-reply-to: <>
  • References: <>


On 07/23/2012 04:30 PM, haihao shen wrote:
> I experimented a frama-c dynamic plugin with the following content in
> makefile:
> # Frama-c should be properly installed with "make install"
> # before any use of this makefile
> FRAMAC_SHARE :=$(shell frama-c.byte -print-path)
> FRAMAC_LIBDIR :=$(shell frama-c.byte -print-libpath)
> PLUGIN_NAME := MyPlugin
> PLUGIN_CMO := register
> include $(FRAMAC_SHARE)/Makefile.dynamic

Looks ok.

> It is okay in Ubuntu when I first make && make install frama-c, and then
> make && make install my plugin. I confirmed by the help message from
> frama-c -help.
> However, when I used the same code under Windows + MinGW and same make
> && make install process, my plugin is not enabled.
> Does anyone encounter such kind of issue or know hoe to fix it?

I'm not aware of specific issues about dynamic plug-in installation 
under Windows+MinGw. What is the result of the following commands after 
installing your plug-in?

$ frama-c.byte -print-plugin-path
$ ls `frama-c.byte -print-plugin-path `
$ frama-c.byte -help