Pre-compiling on OSX may break about tuareg HOT 6 CLOSED

For info: this has been verified with versions 22.1.1 and 24.4.1 (console and "app")

from tuareg.

Is there a way to reliably detect that the "Emacs app" is present? What is the OPAM flag to use so compilation takes place except on OSX?

from tuareg.

The easiest would be to not run the compilation by default in the
OPAM package.

Also, installation via M-x list-packages RET would eliminate
the problem.

    Stefan

from tuareg.

installation via M-x list-packages RET would eliminate the problem.

Absolutely but they want to automate the whole installation (Tuareg being only one component).

There is already an attempt at detecting the app version on OSX. Could you please tell me how to refine it? — I do not have a mac.

from tuareg.

Indeed, that works (it is'nt yet in the OPAM package, but I had success with pinning this git); although I am not sure it is possible to use the compiled code and remain portable in the general case. In the case above, the newer version works for Emacs.app but breaks the text-mode emacs (although with a cleaner error: "file xxx was compiled for Emacs version 23 or later"). And on OSX, there may also be an Aquamacs in the mix...

Even in the general case, it's possible that the system Emacs is changed, and that may break an already compiled Tuareg. On binary distributions, this is handled with hooks that'll register all .elc and make sure they are up-to-date whenever Emacs changes, but we don't have a mechanism to track system dependencies (yet -- there a are plans for this, see https://github.com/ocaml/opam/blob/master/doc/design/depexts-plugins)

So I am afraid that the only way to guarantee it won't break, at the moment, is to install no compiled files from the OPAM package ; the post-message may provide a hint on compiling, or installing through M-x list-packages...

from tuareg.

The upcoming opam file only installs .el files — as you did for earlier versions.

from tuareg.