You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running into a cross-compilation related issue with opam and dune.
Currently dune has a pretty good support for cross-compilation via findlib toolchains. It correctly separates compilation artefacts for different targets. When a findlib toolchain is used with -x TOOLCHAIN, dune, in addition to producing a PKG.intsall file for the default context, will also produce a PKG-TOOLCAHIN.install file. This works perfectly!
But, the problem is that opam doesn't know about these -TOOLCHAIN.install files and only looks for PKG.install files.
Is there a way to instruct opam install to look for additional install files described above? I'm looking for a solution that does not require changes to the original package.
The text was updated successfully, but these errors were encountered:
rizo
changed the title
OCamlfind toolchain install files produced by dune are not installed.
Install files for alternative ocamlfind toolchains are not installed.
May 22, 2020
On install, opam only check for pkg.install file, and there is no way to specify another filename. The only one is to change the opam file (of called command) to move/copy of the generated install file.
Why and what are the generated pkg-toolchain.install files?
I'm running into a cross-compilation related issue with opam and dune.
Currently dune has a pretty good support for cross-compilation via findlib toolchains. It correctly separates compilation artefacts for different targets. When a findlib toolchain is used with
-x TOOLCHAIN
, dune, in addition to producing aPKG.intsall
file for the default context, will also produce aPKG-TOOLCAHIN.install
file. This works perfectly!But, the problem is that opam doesn't know about these
-TOOLCHAIN.install
files and only looks forPKG.install
files.Is there a way to instruct
opam install
to look for additional install files described above? I'm looking for a solution that does not require changes to the original package.Might be related to: #2476.
The text was updated successfully, but these errors were encountered: