Don't use the cc-options from packages when compiling .hc files
authorSimon Marlow <marlowsd@gmail.com>
Thu, 21 Aug 2008 15:55:49 +0000 (15:55 +0000)
committerSimon Marlow <marlowsd@gmail.com>
Thu, 21 Aug 2008 15:55:49 +0000 (15:55 +0000)
commit39271273d6b1fd2cdfe92be1fa30a7eec3cc9107
tree8d13d679ffadb362488724c417d2a6fa798e1e04
parentcc45450cbe5031f9f90fcc44932a9ff1dd36efd2
Don't use the cc-options from packages when compiling .hc files
Now that we don't include any header files in .hc apart from our own,
the cc-options from packages are at best superfluous, so don't pass
them.

We still pass them to .c compilations, although I've just made changes
to Cabal so that cc-options from a .cabal file are not copied into the
InstalledPackageInfo.  Most uses of cc-options in Cabal are clearly
intended to be local to the package, but they were being propagated
everywhere, almost certainly unintentionally.

The way is left open for Cabal to allow packages to specify cc-options
that get propagated in the future, if we find a use case for this.
compiler/main/DriverPipeline.hs