One year later, take-two on transitioning from make to dune for an OCaml-based PL course. We have a course library, say, code.cma, stored in a folder outside the dune workspace, say /Users/studentX/lib/, several course projects use the definitions in this course library.
Instead of trying to share a code.cma file, perhaps you could distribute an opam/dune project skeleton with the library source code,
code.ml? Then the problem of trying to tell dune where code.cma is goes away :-)
I could be wrong, but it seems this setup (with a standard site library code.cma) is pretty common,
I've never heard of it. From what I understand, OCaml, opam, and dune all heavily encourage compiling projects from source because of potential system/architecture differences.
Regards,
Yawar