17:13 <olle> Here’s a general Mirage question: is jbuilder now the build tool?

17:13 <olle> Or, am I just seeing dependent packages of Mirage use jbuilder to build themselves?

17:15 <hannes> olle: jbuilder is a pretty new build tool which seems to get some traction. it is used by several MirageOS libraries, but not all of them.

17:16 <olle> It is _a_ new build tool, not _the_ new build tool. Good clarification.

17:16 <hannes> olle: mirage itself still uses ocamlbuild + ocamlfind, since jbuilder does (not yet!?) have a "cross compilation" story (where mirage uses the same architecture, but has to link different C libraries, and a custom OCaml runtime for kvm/xen/..)

17:20 <olle> Thanks again for the specificity.

17:22 <hannes> thanks for asking!

17:23 <hannes> I suspect by now, there are at least 4 different build systems involved in a mature MirageOS unikernel: oasis (using ocamlbuild), topkg (using ocamlbuild), likely some Makefile / shell scripts (e.g. mirage-xen-*), jbuilder...

17:27 <olle> What are the supported arch’s of Mirage, at the moment? How tiny a computer can run a Mirage? A tablet?

18:40 <hannes> olle: the architectures supported are amd64 (also known as x86_64), arm32 and xen (unclear when this was used last), arm64 and kvm (with an unreleased solo5, but in master)

18:40 <hannes> so tablets should be in scope

18:41 <hannes> cubieboard is in scope -- used to work 2 years ago (it has support for vt-x), raspberry not atm (since no vt-x)