coq-club AT inria.fr
Subject: The Coq mailing list
List archive
- From: Guillaume Melquiond <guillaume.melquiond AT inria.fr>
- To: coq-club AT inria.fr
- Subject: Re: [Coq-Club] Coq plugins depending on external libraries
- Date: Wed, 01 Apr 2015 16:50:09 +0200
On 01/04/2015 16:43, Ali Assaf wrote:
As you can guess, this is very cumbersome. Has anyone faced this problem
before? Is there any way to solve it in a portable way (by not
hardcoding the paths in MyPlugin.v)? I tried looking for a way to
package the libraries with the plugin but so far I have not been successful.
That is an issue we also have for the Why3 plugin for Coq. We solve it by packaging the libraries with the plugin. When producing the .cmxs file for the plugin, we are passing all the .cmxa files of the libraries we are interested in on the command line.
Best regards,
Guillaume
- [Coq-Club] Coq plugins depending on external libraries, Ali Assaf, 04/01/2015
- Re: [Coq-Club] Coq plugins depending on external libraries, Guillaume Melquiond, 04/01/2015
- Re: [Coq-Club] Coq plugins depending on external libraries, Ali Assaf, 04/01/2015
- Re: [Coq-Club] Coq plugins depending on external libraries, Guillaume Melquiond, 04/01/2015
Archive powered by MHonArc 2.6.18.