Automatic inclusion of a dependency share folder in the install tree?

Ecosystem
, ,
1

Question

Is there a way to include via dune rules a dependency’s share folder in my own project install tree? Or should I vendor those files?

Context

I am writing a barebone Python API for CAISAR.

My idea is to build statically CAISAR’s binary (with a huge help from this blog post by OCamlPro!), then ship it with Python to be able to install CAISAR using usual Python librairies like pip install caisarpy (note this is the first time I attempt to do this, so taking any advice here!). Building the binary is done, but I struggle to ship external resources.

CAISAR relies extensively on why3 to provide default configurations for provers and drivers (everything that is shipped under Why3’s share folder). During development, said files are available in the local opam switch.

For a binary distribution, we do not have a local opam switch, so I would like to include the content of Why3’s share folder in CAISAR install tree (for instance with dune-site).

1 Like