Antonio Nuno Monteiro

I added a new proposal in https://github.com/ocaml/dune/issues/10630 that would replace this one.

> I understand describe is a "read-only" subcommand, `dune describe pp` is not read-only, at least, since it builds the ppx pipeline and preprocesses the files.

at least for the ocamllex case it's easy to see why the target is expected to be in the same dir as the dune file: https://github.com/ocaml/dune/blob/2a4a5bf6b904549dccd580904bff52e49a8ec8f2/src/dune_rules/stanzas/rule_conf.ml#L215-L220

and for menhir: https://github.com/ocaml/dune/blob/2a4a5bf6b904549dccd580904bff52e49a8ec8f2/src/dune_rules/menhir/menhir_rules.ml#L100-L103

@emillon changed this to be just about menhir, and renamed the test case to point to #10301.

ping @emillon

> I guess Dune duplication checks come before actually checking if the public libraries are being installed in separate switches? Indeed, I believe they're coming from `scope.ml`, when creating the...

@rgrinberg thanks, I made the description a bit more clear.

Thanks for your review, @emillon. I added a stable URL and a `seealso` block.

Ah right, we should be passing `-ccopt -static` to `ocamlopt_flags`. I usually add that in an env stanza under a static profile.