package mirage-fs

Build not checked
  1. Overview
  2. Docs
MirageOS signatures for filesystem devices

Install

dune-project
 Dependency

Authors

Maintainers

Sources

mirage-fs-v2.0.0.tbz
sha256=09a2c0cfc597d6753b853e08f1d59c58db914afa9251b9bd76f0715caecf7925
md5=b391694a35550ca52439562a31577bb6

Description

mirage-fs provides the [Mirage_fs.S][fs] and [Mirage_fs_lwt.S] signatures the MirageOS filesystem devices should implement.

Tags

org:mirage

Added to opam-repository:

README

mirage-fs — MirageOS signatures for filesystem devices

Build Status

mirage-fs provides the [Mirage_fs.S][fs] and [Mirage_fs_lwt.S] signatures the MirageOS filesystem devices should implement.

Installation

mirage-fs can be installed with opam:

opam install mirage-fs

If you don't use opam consult the opam file for build instructions.

Documentation

The documentation and API reference is generated from the source interfaces. It can be consulted online or via odig doc mirage-fs.

License

mirage-fs is distributed under the ISC license, see the LICENSE.md file for its text.

Dependencies (4)

  1. mirage-device >= "1.0.0" & < "2.0.0"
  2. fmt
  3. dune
  4. ocaml >= "4.04.2"

Dev Dependencies

None

Optional Dependencies

None

Used by (4)

  1. docteur-unix < "0.0.3"
  2. fat-filesystem < "0.14.0"
  3. mirage-fs-lwt
  4. mirage-types >= "3.6.0"

Conflicts

None

Build status

Results of building mirage-fs with each compiler on check.ci.ocaml.org, run of against opam-repository 7cdc698. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

This version is not in the latest run; the versions below are.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
4.0.0 good good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure