Build/library system

[jonaprieto]

Our module system allows us to split our development into multiple files, making it easier to develop libraries. However, we do not have full support for library development at the moment (v0.2.0). To build a MiniJuvix project, as it is now, all the MiniJuvix code that a project needs must be inside the same folder. This can be inconvenient for build projects in general, as they may need to use external MiniJuvix libraries. However, I believe that addressing this problem at an early stage can quickly reveal other issues that may be easier to solve now than when the compiler grows older. Furthermore, making it easier for the developer to build their projects, possibly using external libraries, can increase the adoption and feedback we can get from our users.

As inspiration, see, for example, cargo the Rust solution to this issue, a combined tool of a build system and package management. https://doc.rust-lang.org/book/ch01-03-hello-cargo.html and https://crates.io/.

A possible list of expected features (w.i.p):

• (Un)register a local library given by its path
  • Register the dependencies listed in the corresponding Yaml file.

Related issues:

• #202

Feel free to suggest other examples, projects, or ideas.