xic VS dune

I cloc'd two compilers for xic, compilers written by cornell students for a compilers class which compile a toy C-like language down to assembly, possibly with some extensions. One compiler was about 11k sloc, the other about 32k. Both compilers are written mainly in OCaml, which is a terse language that is pretty optimal for compiler development, but have some java code in them as well. I think these are good examples of mostly minimal compilers which compile a C-like down to asm, though they are very rudimentary compared to more serious projects. I want to emphasize that this is not very meaningful without more details about what you are looking to know.

Here's a compiler for a C-like language written in OCaml (note: I am not one of the authors though I did take the class). Despite it being a college project I think it shows very clean design and particularly good use of preprocessors. All of the details for the language and stuff is linked at the bottom. It's a relatively small codebase of course but I think this is good educationally.

If you are using the dune build system, add the tag(s) to your dune-project file's package stanza. E.g.:

One way to get around this is to modify the api/dune file with (include_subdirs qualified); this means that every subdirectory of api/ can be referenced by module namespacing and we don't have to write dune files for every route (or pages) folder. However, the OCaml LSP does not like it and red squiggles will show up in the editor (although the app with still compile without errors). Trying to develop the app knowing those red squiggles cannot be vanquished would drive me nuts, so instead of using (include_subdirs qualified) I just wrote dune files for every route (and page) which gets rid of the red squiggles.

2) Neither would having all source/targets specified, as that would entail listing them all in the dune file as wildcard rules is apparently still not a thing: https://github.com/ocaml/dune/issues/307

There is a small example on the dune home page: https://dune.build/

Dune (https://dune.build/) is the preeminent build tool for OCaml development. I don't love its input syntax (s-expressions), and I sometimes miss the ability to write high-level functions to reduce boilerplate (especially for unit tests), but it always gets the dependencies right, and it's fast. This is in stark contrast to some of my experiences with various other build systems, and I am super happy that the default option for OCaml build systems is so good.

It's still weird because dune's own site only makes Jane Street references: https://dune.build/.

ONE of the big benefits of OCaml is its powerful REPL (also called the toplevel), the interactive command-line utility where you can load modules, type in and execute code, and see its results. The modern REPL, utop, has powerful auto-completion and integration with the build system dune, which enables productive workflows like loading an entire project's libraries in the REPL and interactively exploring them.