forked from haskell/cabal
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add --cabal-ghc/-pkg flags to 'configure'
Add 'SetupWrapperFlags' with flags to configure a path to GHC and GHC-PKG to build 'Setup.hs'. This is an initial draft implementation done primarily for code review of the basic design decision, so only the configure and the install commands respect these flags.
- Loading branch information
Sven Heyll
committed
Nov 2, 2014
1 parent
1f41dbf
commit 06c2501
Showing
7 changed files
with
213 additions
and
83 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
06c2501
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need a special
SetupWrapperFlags
record - information about the build compiler is not specific to setup scripts and could be potentially used for other things.The logical place to put this stuff is
ConfigFlags
andLocalBuildInfo
. Add aconfigBuildHcPath
flag toConfigFlags
, and abuildCompiler
field toLocalBuildInfo
. This will be consistent with already-existingconfigHcPath
andcompiler
.Then you can just pass
LocalBuildInfo.buildCompiler
tosetupWrapper
via theSetupScriptOptions.useCompiler
field.06c2501
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok thanks alot! I will exactly that.
06c2501
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any hints on testing?
06c2501
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Compile a
build-type: Custom
package with-v3
and check that the right compiler is used.