In #6931 i showed that dynamically linked binaries have issues being executed on Windows when out of the context of the internal cgywin (PowerShell or third party cygwin terminal). I'm not exactly sure how to fix this kind of issues yet, but maybe a environment variable or something like that could be added to the output of opam env to make these DLLs reachable from native shells. If it's not possible, maybe adding a new opam run command that would spawn a new internal cygwin shell might be a solution. Idk
In #6931 i showed that dynamically linked binaries have issues being executed on Windows when out of the context of the internal cgywin (PowerShell or third party cygwin terminal). I'm not exactly sure how to fix this kind of issues yet, but maybe a environment variable or something like that could be added to the output of
opam envto make these DLLs reachable from native shells. If it's not possible, maybe adding a newopam runcommand that would spawn a new internal cygwin shell might be a solution. Idk