Thanks for your answer!
I’ve started again using 4.06.0 (*) and opam-cross-esp32#v0.2
opam switch create 4.06.0+32bit 4.06.0+32bit
eval $(opam env)
opam repo add opam-cross-esp32 'https://github.com/well-typed-lightbulbs/opam-cross-esp32.git#v0.2'
Then I try
opam install mirage and it doesn’t try to pull any esp32-specific package. I tried
opam install mirage.3.0.8b+esp32 but again, it doesn’t try to pull any (other) esp32-specific package. For instance, opam selects
ipaddr-5.0.1 while your repo shows there’s only
ipadrr-esp184.108.40.206. If I try to install
ipaddr-esp32, it pulls many many esp32-specific packages, including
ocaml-esp32. Do you remember why there’s only
mirage and not
mirage-esp32 in the opam repo?
My initial issue was that I was not able to run
mirage config -t esp32 because
-t did not exist in whatever was installed then.
(*) well, first using 4.06.1 but cross compilers need a native compiler of the exact same version so I had to start again; I think I’m the one who made it that way but I had completely forgotten about that.