with #41 in mind, other mirage-solo5-* libraries have already been ported to dune (mirage-solo5 seems to be the only one which still uses topkg/ocamlbuild). In the light of the reviews of #47 (which is superseeded by this PR), I pushed a commit here that I had lying around for some while. It keeps the names (libmirage-solo5_bindings.a for the C stubs, built with the pkg-config'd ocaml-freestanding CFLAGS (by calling out to cflags.sh which calls pkg-config), the OCaml module is still OS), but ports the build system to dune.
the advantage from a maintenance point of view is that there's no longer any need to remember topkg and dune-release runes. existing mirage-solo5-* packages (esp. mirage-net-solo5) install fine with this PR; also an end-to-end tested unikernels (from mirage-skeleton) work well.
with #41 in mind, other mirage-solo5-* libraries have already been ported to dune (mirage-solo5 seems to be the only one which still uses topkg/ocamlbuild). In the light of the reviews of #47 (which is superseeded by this PR), I pushed a commit here that I had lying around for some while. It keeps the names (
libmirage-solo5_bindings.a
for the C stubs, built with thepkg-config
'd ocaml-freestanding CFLAGS (by calling out tocflags.sh
which calls pkg-config), the OCaml module is stillOS
), but ports the build system to dune.the advantage from a maintenance point of view is that there's no longer any need to remember topkg and dune-release runes. existing mirage-solo5-* packages (esp. mirage-net-solo5) install fine with this PR; also an end-to-end tested unikernels (from mirage-skeleton) work well.