Cabal: Take into account compilerBuildWay when computing final library ways
In the profiling dynamic patch I made a mistake when computing the needed ways for a build. When building an executable, the Haskell modules need to be built * For the final link way * For the build way of the compiler if TH is enabled Before this patch, the modules were being built for all the configured library ways, which built modules in more configurations than the previous version of Cabal. Fixes #10418 (cherry picked from commit 27c26688)
Showing
- Cabal/src/Distribution/Simple/GHC/Build.hs 17 additions, 3 deletionsCabal/src/Distribution/Simple/GHC/Build.hs
- cabal-testsuite/PackageTests/BuildWays/p/CHANGELOG.md 5 additions, 0 deletionscabal-testsuite/PackageTests/BuildWays/p/CHANGELOG.md
- cabal-testsuite/PackageTests/BuildWays/p/p.cabal 18 additions, 0 deletionscabal-testsuite/PackageTests/BuildWays/p/p.cabal
- cabal-testsuite/PackageTests/BuildWays/p/src/MyLib.hs 4 additions, 0 deletionscabal-testsuite/PackageTests/BuildWays/p/src/MyLib.hs
- cabal-testsuite/PackageTests/BuildWays/q/CHANGELOG.md 5 additions, 0 deletionscabal-testsuite/PackageTests/BuildWays/q/CHANGELOG.md
- cabal-testsuite/PackageTests/BuildWays/q/app/Main.hs 7 additions, 0 deletionscabal-testsuite/PackageTests/BuildWays/q/app/Main.hs
- cabal-testsuite/PackageTests/BuildWays/q/q.cabal 19 additions, 0 deletionscabal-testsuite/PackageTests/BuildWays/q/q.cabal
- cabal-testsuite/PackageTests/BuildWays/setup.test.hs 10 additions, 0 deletionscabal-testsuite/PackageTests/BuildWays/setup.test.hs
- changelog.d/i10418 13 additions, 0 deletionschangelog.d/i10418
Loading
Please register or sign in to comment