From PowerShell, calling opam publish (which depends on gmp) will fail and exit code 127 (0xc0000135) without any error message. This is due to gmp being dynlinked and unable to reach libgmp-10.dll that opam installed via its depexts system.
Calling opam-publish directly does the same thing, however calling opam exec -- opam-publish works fine. This is because (i think), `opam exec runs binaries as if they were ran through the cygwin root and thus the DLL is found correctly.
I think calling opam-publish as a plugin (i.e. opam publish) should also do the same thing.
From PowerShell, calling
opam publish(which depends ongmp) will fail and exit code 127 (0xc0000135) without any error message. This is due to gmp being dynlinked and unable to reachlibgmp-10.dllthat opam installed via its depexts system.Calling
opam-publishdirectly does the same thing, however callingopam exec -- opam-publishworks fine. This is because (i think), `opam exec runs binaries as if they were ran through the cygwin root and thus the DLL is found correctly.I think calling opam-publish as a plugin (i.e.
opam publish) should also do the same thing.