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 working with docker-base-images which has vendored dependencies. I'm trying to execute a program that's defined in one of the vendored dependencies, ocluster. If dune doesn't find the dependencies of ocluster in the current switch, it hints the external-libs-deps command, but when running that function it does not know anymore how to build that executable.
Is external-lib-deps using a different name resolution scheme from exec? Either they could use the same, or the hint should point to the correct path.
Changing directories to that vendored dependency (or symlinking to it) doesn't help as Dune is smart enough to position itself at the project's root. My current workaround is to clone separately the dependencies and build them once.
EDIT: or I can use the path to the binary as is:
$ dune external-lib-deps --missing ocluster/bin/scheduler.exe
Error: The following libraries are missing in the default context:
- digestif
- dune-build-info
- obuilder
- psq
Hint: try:
opam install digestif dune-build-info obuilder psq
The text was updated successfully, but these errors were encountered:
I'm working with docker-base-images which has vendored dependencies. I'm trying to execute a program that's defined in one of the vendored dependencies, ocluster. If dune doesn't find the dependencies of ocluster in the current switch, it hints the external-libs-deps command, but when running that function it does not know anymore how to build that executable.
Is external-lib-deps using a different name resolution scheme from exec? Either they could use the same, or the hint should point to the correct path.
Changing directories to that vendored dependency (or symlinking to it) doesn't help as Dune is smart enough to position itself at the project's root. My current workaround is to clone separately the dependencies and build them once.
EDIT: or I can use the path to the binary as is:
The text was updated successfully, but these errors were encountered: