Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Specify include and library paths that are used for building the package only #188

Closed
bos opened this Issue May 24, 2012 · 1 comment

Comments

Projects
None yet
2 participants
Contributor

bos commented May 24, 2012

(Imported from Trac #195, reported by @dcoutts on 2007-12-17)

From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293523

Specify include and library paths that are used for building the
package only, and do not end up in the GHC packages file.
I think this needs more explanation.

There is certainly a use case for includes that are used to pre-process Haskell code since they are never needed when building dependent packages. On the other hand, library paths to find libraries to link to are always required by dependent packages as far as I know since to link an executable using a package that uses a library we have to specify the library and search path.

There is no way with GHC to limit where a C header file might be needed. If a header file is needed to compile a package, then the header file might also be needed to compile code that uses the package due to cross-package inlining. If GHC does gain the feature to limit the scope of where C headers are required then we will want to support that in Cabal, possibly via package-local headers.

Owner

tibbe commented May 5, 2014

Closing as there's been no activity in years.

We're cleaning up the bug tracker to make it useful again and are thus closing bugs that haven't seen any activity in a long time. Please re-open (or file a new bug) if the problem reappears.

@tibbe tibbe closed this May 5, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment