Open ivg opened 8 years ago
I don't think codoc
is up-to-date with this library at the moment. odoc is more up-to-date, can you reproduce the issue with that?
There have been a few Lazy.Undefined
bugs, but all of the ones I'm aware of have been fixed, so I'm interested if you have discovered another case.
Do you have suggestions on how to switch opam-doc from codoc
to odoc
?
Hmm, the best thing might be to wait a couple of weeks and then try with opkg which subsumes opam-doc and supports odoc.
(Wait a couple of weeks because opkg should be released by then)
Just don't try opkg odoc
right now there's still a bug in odoc
that will muddy your cwd
.
(opkg ocamldoc
is fine if you are interested).
That's alright, we can wait, so far we felt back to the argot for our documentation. But we're anticipating a move to the newer infrastructure, so don't hesitate to use us a alpha testers.
At first I created an dsheets/codoc#95 issue in
codoc
repository, but it looks like that this repository is more suitable. On the link phase I've got aLazy.Undefined
exception. Not sure if it helps, but here is the backtrace:I will be happy to provide more info, don't hesitate to ask. (It could be hard to reproduce, though, but maybe I can just tar-ball the opam folder or maybe just the output folder of
opam doc
).