Sanity check: omake vs dune progress counters report different number of things to compile

@mbacarella wrote:

At the top-level of my project I run omake, which provides status of compilation:

[====     ]  00803 / 04960

(then a git clean -fx happens to eliminate all build artifacts)

When I do the same with dune build --profile=release, I get a higher number:

Done: 3580/6118 (jobs: 4)

Is dune doing more work, or is it simply accounting for number of things left to-do differently?

I’m using dune 2.0 in my project file, so it should only be building native. Additionally, the same set of .exe files are generated by both omake and dune (and I confirm no .bc files appear). The counts of generated .cmx files are the same as well, +/- 2.

If it matters, dune takes about 5% longer to finish building the whole tree than omake.

EDIT: I’m aware that the number of things to-do may increase as the build progresses, but even when they’re both at 99% done they’re still about a thousand total to-do items apart.

Posts: 8

Participants: 3

Read full topic