Hello,
I am thinking about opam packages which rely on some system-wide installation
of a dependency.
E.g. nlopt-ocaml relies on nlopt being installed in the right place.
Is there a way to support easily the case where the required dependency
has been user-installed (so in user-space), instead of system-wide?
We need a way to tell dune where the header files (.h) are located, we also
need a way to tell where the compiled library is (.so).
At runtime, I know that setting LD_LIBRARY_PATH does the right thing.
But, I am annoyed at compile time.
Thanks,
F.
2 posts - 2 participants