-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does hpack not use the includes
property?
#355
Comments
@sol Would you like a PR for this ? I had to drop using hpack for a specific project because of this limitation. |
Okay, I solved it by using the field |
Can this be documented @psibi? |
Follows the pattern of existing `install-includes`.
Follows the pattern of existing `install-includes`.
Follows the pattern of existing `install-includes`.
I am going to close this issue because the short answer is that GHC has ignored the |
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
This is useless at best, and a common source of confusion. haskell/cabal#10145 sol/hpack#355
Cabal has the
includes
property: https://www.haskell.org/cabal/users-guide/developing-packages.html#pkg-field-includesWhich allows you to specify the C headers that should be included when we are compiling C code. How come this is ignored by Hpack? How does Hpack specify that C headers are needed when compiling some C code with
c-sources
?The text was updated successfully, but these errors were encountered: