Stephen Sherratt

These are my notes for manually building the compiler from source on windows using the x86_64-w64-mingw32 toolchain. The goal is to automate as much of this as necessary within dune,...

Update on manually building the compiler toolchain on windows: [this script](https://github.com/gridbugs/dune/blob/windows-hacks/build-ocaml.sh) from my fork of dune is a simplified version of the instructions in the previous comment and I recommend...

I have a branch on my fork of dune that supports package management on windows: https://github.com/gridbugs/dune/tree/windows-hacks See the differences between that branch and its latest upstream ancestor (bca9e656b61f7d2b827016b7fd9b1a682c690a7b) for all...

It appears that dune always picks an ocaml toolchain when it starts, and part of that involves running `ocamlc -config`. If a lockdir is present then dune will use the...

I'll start working on deferring running `ocamlc -config` until it's needed to get a feel for how much work it will be.

It looks like it's forced while setting up the rules of the project (which if I'm not mistaken happens on every `dune build` command regardless of the target). For example...

Here's another idea. `Lib_config.t` is defined like this: ```ocaml type t = { has_native : bool ; ext_lib : Filename.Extension.t ; ext_obj : Filename.Extension.t ; os_type : Ocaml_config.Os_type.t ; architecture...

Ah I hadn't considered cross compilation. @rgrinberg what do you think about [my previous comment](https://github.com/ocaml/dune/issues/11038#issuecomment-2448928633) about `Lib_config.t` being needed to set up the project rules? Is it the case that...

I recently got a couple of packages building on Windows with Dune package management (the packages were ocamlformat and ocaml-lsp-server). It required working around several issues. I've made [this repo](https://github.com/gridbugs/dune-windows-repros)...

TL;DR I suggest approaching package management much more like debian and providing a community repo with which is entirely maintained by package authors. I think there's some tension around opam...