-
Notifications
You must be signed in to change notification settings - Fork 37
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
cabal-helper tries to configure a component named package:setup that does not exist. #95
Comments
To add more context: cabal v2-build --with-ghc=C:\Users\flip111\AppData\Local\Programs\stack\x86_64-windows\ghc-8.6.5\bin\ghc.exe --with-ghc-pkg=C:\Users\flip111\AppData\Local\Programs\stack\x86_64-windows\ghc-8.6.5\bin\ghc-pkg.exe --with-haddock=C:\Users\flip111\AppData\Local\Programs\stack\x86_64-windows\ghc-8.6.5\bin\haddock.exe --project-file=C:\Users\flip111\haskell\cabal\cabal.project --builddir=C:\Users\flip111\haskell\cabal\dist-newstyle --only-configure cabal-install:exe:cabal cabal-install:setup Note the last target
EDIT: Verbose output of cabal-helper (executed with hie) on a similar project (not cabal)
|
The package config looks like this: Package {pPackageName = "fprog", pSourceDir = "D:\\Privat\\Documents\\programming\\haskell\\fprog\\.", pCabalFile = CabalFile "D:\\Privat\\Documents\\programming\\haskell\\fprog\\.\\fprog.cabal", pFlags = [], pUnits = Unit {uUnitId = UnitId "fprog-0.1.0.0-inplace", uPackage = Package {pPackageName = "fprog", pSourceDir = "D:\\Privat\\Documents\\programming\\haskell\\fprog\\.", pCabalFile = CabalFile "D:\\Privat\\Documents\\programming\\haskell\\fprog\\.\\fprog.cabal", pFlags = [], pUnits = ()}, uDistDir = DistDirLib "D:\\Privat\\Documents\\programming\\haskell\\fprog\\dist-newstyle\\build\\x86_64-windows\\ghc-8.6.5\\fprog-0.1.0.0", uImpl = UnitImplV2 {uiV2ComponentNames = [ChExeName "fprog",ChSetupHsName], uiV2Components = ["fprog:exe:fprog","fprog:setup"], uiV2OnlyDependencies = False}} Note UnitImplV2 {uiV2ComponentNames = [ChExeName "fprog",ChSetupHsName], uiV2Components = ["fprog:exe:fprog","fprog:setup"], uiV2OnlyDependencies = False} which contains |
Previously we would pick up Stack's Cabal version with ghc-pkg on the global package-db. This however ignores that Stack also supports custom Setup.hs with the Cabal version from the snapshot instead. In cabal v2-build we have a similar problem. We used to assume that plan.json's cabal-lib-version is used uniformly across units but this is similarly untrue. To fix both of these we re-stage the cabal version query to after reconfiguring a unit, then we can just lookup the Cabal version in setup-config. Fixes #95
Previously we would pick up Stack's Cabal version with ghc-pkg on the global package-db. This however ignores that Stack also supports custom Setup.hs with the Cabal version from the snapshot instead. In cabal v2-build we have a similar problem. We used to assume that plan.json's cabal-lib-version is used uniformly across units but this is similarly untrue. To fix both of these we re-stage the cabal version query to after reconfiguring a unit, then we can just lookup the Cabal version in setup-config. Fixes #95
Previously we would pick up Stack's Cabal version with ghc-pkg on the global package-db. This however ignores that Stack also supports custom Setup.hs with the Cabal version from the snapshot instead. In cabal v2-build we have a similar problem. We used to assume that plan.json's cabal-lib-version is used uniformly across units but this is similarly untrue. To fix both of these we re-stage the cabal version query to after reconfiguring a unit, then we can just lookup the Cabal version in setup-config. Fixes #95
Hello,
we ran into an issue in another project over here haskell/haskell-ide-engine#1638 (comment)
is this something that can be fixed in cabal-helper ?
The text was updated successfully, but these errors were encountered: