macOS: serapi loads Coq .vo from compile time path about coq-serapi HOT 5 CLOSED

Hi @MSoegtropIMC , I'm sorry it took you 4 months to get sertop running, I was not aware you were having problems, I guess most of the time is due to path length issues? Is there any other issue that I'm not aware of?

I think the difference in this case is that the Linux snap is likely setting COQLIB whereas in OSX you are using a different relocation method?

sertop determines the path for coqlib in an almost standard way:

• command line parameter --coqlib
• search for COQLIB env var
• if not use the path passed to configure

So I'd suggest you set COQLIB for the smoke test for now, IMHO that's an acceptable workaround for users too if the auto-detection is not working properly.

As I've mentioned some other times, I'd be great to refactor sertop and Coq's init code so they share all this logic. As of today this is not the case as sertop added its own init code back in the day when Coq's API didn't allow to be used.

Later, Coq API was refactored to support different methods, but it was done without coordination with the other toplevels. So as of today some coding needs to happen to unify this, but I'm afraid I don't have the resources to take care of that myself :(

from coq-serapi.

Yes, most of the issues were path length issues on Windows, and this time it really required quite a bit of restructuring of the Coq Platform path structure to make it work (with 1 character margin left). If the paths get any longer - without fixing in either OCaml or dune - I need to disable it on Windows.

I am quite sure that COQLIB is not set in the Windows and Mac case, but indeed I can't exclude that it is set in the snap case via the alias mechanism - it is quite possible. So this explains the difference between MacOS and Linux snap, but it doesn't explain why it works on Windows. Is it possible that you have special handling on Windows?

from coq-serapi.

We don't have anything specific for Windows, but maybe you update Coq configure in a different way?

That would explain the difference.

from coq-serapi.

I am using opam to install coq and serapi, so nothing special I am aware of.

Also on all platforms we are talking about relocated installations, where the final path does not match the configure path.

For coqc on Windows this works by an environment file which is written by the installer, but serapi does not use this (afaik). Also there is a mechanism in ocamlfind to find libraries after relocation (as discussed), but this does not influence finding .vo files.

from coq-serapi.

Next SerAPI release will be the last, so IMHO not worth fixing this.

SerAPI has been now replaced by all purposes by coq-lsp, which should integrate with the platform better.

from coq-serapi.