The following problem exists in cabal-2.4 to cabal-3.4.
In $HOME/.cabal/config I have
library-profiling: True
When compiling with cabal v2-build I cannot disable profiling locally, neither using command-line option --disable-library-profiling nor in cabal.project.local with library-profiling: False. It's just ignored and cabal continues building the profiled version. It does not harm, but increases build time considerably and sometimes I just want a quick build without profiling. Ok, there is an instance where it harms: When I want to build ghc-vis it says that it cannot be build with profiling and I should disable it using --disable-library-profiling, although that's precisely what I did.
The following problem exists in
cabal-2.4
tocabal-3.4
.In
$HOME/.cabal/config
I haveWhen compiling with
cabal v2-build
I cannot disable profiling locally, neither using command-line option--disable-library-profiling
nor incabal.project.local
withlibrary-profiling: False
. It's just ignored andcabal
continues building the profiled version. It does not harm, but increases build time considerably and sometimes I just want a quick build without profiling. Ok, there is an instance where it harms: When I want to buildghc-vis
it says that it cannot be build with profiling and I should disable it using--disable-library-profiling
, although that's precisely what I did.