OCaml 4.11 support

support for OCaml 4.11 (#214 by @kit-ty-kate)

OCaml 4.09 and 4.10 support

v3.3.2

[ci skip] changes for 3.3.2

OCaml 4.08.0 support and fix CFLAGS generation

• Fix CFLAGS generation with repeated spaces on Linux (#210 @TheLortex)
• Add support for 4.08 final release (continued from #206 by @avsm)

Expose flags via files to help Dune and support OCaml 4.08

• Add support for OCaml 4.08 (#206 by @anmonteiro)
• libxenasmrun.a is symlinked in the ocaml directory in order to be able to use ocamlopt's -runtime-variant option.
• Expose flags through files as well as pkg-config (#205 by @TheLortex). Instead of pkg-config, one can use the following files to get compilation flags:
  • mirage-xen-ocaml/libs
  • mirage-xen-ocaml/cflags
  • mirage-xen-posix/minios-cflags
  • mirage-xen-posix/minios-libs
  • mirage-xen-posix/posix-cflags
  • mirage-xen-posix/posix-libs
    With dune this allows us to write %{lib:mirage-xen-posix:posix-libs} to get the flags instead of having a script invoking pkg-config mirage-xen-posix --libs.

Support OCaml 4.06 and 4.07

• add support for OCaml 4.06 and 4.07 in the xen backend (#205 by @anmonteiro)
• update opam metadata to 2.0 format (@avsm)

META files

mirage-xen-posix and mirage-xen-ocaml now install a META file to be recognized by build systems

3.0.6

CHANGES:

• xen: do not use opam config exec during the build to be compatible
  with opam2 (#201, @reynir)

support ocaml 4.05.0 in xen

xen: add support for OCaml 4.05.0 (@talex5, #195)

support OCaml 4.04.2

mirage-xen-ocaml: remove support for versions of OCaml older than 4.04.2 , and add support for OCaml 4.04.2. For older revisions of OCaml, use an older revision of mirage-xen-ocaml.

Future releases of xen will be using ocaml-freestanding, so consider this release an "end of life" for this particular MiniOS stream.

Restore the io-page link temporarily

• xen: we need io-page-xen because

  • mirage-xen depends on xen-gnt (for suspend/resume callbacks)
  • xen-gnt depends on io-page (to represent the types of page mappings)
  • io-page needs either io-page-unix or io-page-xen. We can't hardcode
    a dependency because it needs to be different on Unix / Xen / Solo5.
    In future we could break the link by adding some kind of pre suspend
post resume callback mechanism and then remove the xen-gnt dependency.

• unix: we need io-page-unix because

  • mirage-types-lwt is in the common set linked into all Unikernels by
    the mirage tool
  • mirage-types-lwt depends on mirage-block-lwt and mirage-net-lwt
  • mirage-block-lwt depends on io-page
  • io-page needs either io-page-unix or io-page-xen. We can't hardcode
    a dependency because it needs to be different on Unix / Xen / Solo5
    In future we could break the link by rethinking the alignment requirements
    of the interfaces. Perhaps FLOW could be unaligned but raw NETIF
    and BLOCKIF aligned?