The getting started instructions are available here: Getting Started.
I now want to share my design of FFI support for alternative backends, which I’m now thinking to be sufficiently extensible and customizable to solve any other backends’ FFI problems.
I use 2 components only, which’re all standarding for a Git repo:
An FFI Provider,
for a pursuit library.
A mirror index
for searching a Python FFI provider repo from a pursuit library’s name and version. I just made one now, at here:
spago build with
pspy backend will use the auto-generated configuration file to decide the mirror to use, e.g., in this auto-generated configuration,
"index-mirror": "default" means we will use the git repo locally stored at
~/.pspy/mirrors/default to look up Python FFI providers, and there’s an instruction in Getting Started about making a
default mirror by
git clone https://github.com/purescript-python/purescript-python-ffi-inde ~/.pspy/mirrors/default
The implementation of a mirror has such an entry point function, tell us which git repo will used for a given pursuit package.