Closed Bodigrim closed 1 year ago
Thank you for the idea. Fixed in HsOpenSSL-0.11.7.5
While maybe helpful for cabal users, this is lop-sided on the side of cabal vs. stack and causes
I think libraries should be agnostic whether one uses cabal or stack to build them.
I never used Stack, so I don't know what instructions for Stack might be (and whether is it possible to detect that Cabal is run from stack). I will happily accept a PR that extends the message with instructions for Stack.
https://github.com/haskell-cryptography/HsOpenSSL/blob/094f7ef6c9ef4dc3eea56802382b1d50c99572d6/Setup.hs#L90-L95
This advice works when you build
HsOpenSSL
itself, but does not whenHsOpenSSL
is only a dependency of the current package:--extra-include-dirs
and--extra-lib-dirs
are applied only to the current package. A more robust suggestion would be to extendcabal.project
with