Port to coqpp.

[ppedrot]

No description provided.

[Zimmi48]

@ppedrot Is the plan to have all plugins exclusively rely on coqpp for 8.10?

[ppedrot]

Indeed.

[Zimmi48]

@ppedrot This PR breaks compatibility with Coq 8.9 (not surprising, but let's say the objective of keeping compatibility with two successive versions of Coq won't have lasted long) so this PR should also remove the line testing Coq 8.9 from the .travis.yml file.

[ppedrot]

@Zimmi48 This should be ready btw.

[Zimmi48]

@ppedrot I forgot but since this is removing the dependency on camlp5, can you remove it from the default.nix too? I was going to say to do the same to the opam file but I realize this file is only present in the v8.8 branch. @fakusb @palmskog: should we copy this file to the v8.9 and master branches as well?

[ppedrot]

Unluckily I have no idea about the Nix language, so please go ahead.

[Zimmi48]

Done.

[Zimmi48]

@ppedrot It turns out that the dependency on camlp5 cannot be removed without change after all:

CAMLOPT -pack -o src/aac_plugin.cmx
ocamlfind: Package `camlp5.gramlib' not found

Do you understand this error?

[ppedrot]

I suspect that this is due to coq_makefile, that still passes the camlp5 library flags to all files it compiles. If we want a transition phase I don't know how to work around this cleanly. Maybe a flag passed to the invocation of coq_makefile?

[Zimmi48]

Well, one solution is to continue depending on camlp5 until the Coq packages are migrated to use dune instead of coq_makefile... For the sake of not blocking this PR, I suggest you force-push to this branch to remove my commit.

[ppedrot]

Gaah. Done.

[palmskog]

@Zimmi48 feel free to copy and adapt the opam file to the v8.9 branch, I was planning to do it myself anyway. Would be good to have in master branch as well, but I was unsure what dependencies even are there.

[Zimmi48]

So @fakusb, this PR looks ready to me. It is need by @ppedrot to be able to merge a PR upstream.

[fakusb]

@Zimmi48 ok, I'm not very knowledgeable in the build infrastructure.
Concerning the opam file: It seems like a good idea, but again I don't have a very deep understanding of opam. If providing properly edited versions of the opam file on the other branches is desired, I can do so tomorrrow.