-
Notifications
You must be signed in to change notification settings - Fork 237
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
How to easily set -Werror
only in the Nix build of things?
#519
Labels
preserved
Keep stale bot away
Comments
michaelpj
added a commit
to michaelpj/plutus
that referenced
this issue
Mar 26, 2020
This proves somewhat annoying, unfortunately. See input-output-hk/haskell.nix#519 for details.
michaelpj
added a commit
to IntersectMBO/plutus
that referenced
this issue
Mar 26, 2020
This proves somewhat annoying, unfortunately. See input-output-hk/haskell.nix#519 for details.
We'd like this ability as well. This was sort of discussed in the following issue: #298 |
+1 I also want this as a stack user because I use the non |
kayvank
pushed a commit
to input-output-hk/marconi
that referenced
this issue
Mar 11, 2023
This proves somewhat annoying, unfortunately. See input-output-hk/haskell.nix#519 for details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A common desire is to set
-Werror
in CI/production builds but not in development builds.It's not clear how to do this best in
haskell.nix
. Options that I can see:package a: ghc-options: -Werror
in yourcabal.project
for all your local packages. (Can't do it globally because that affects dependencies: ghc-options applies to all dependencies, not just local packages haskell/cabal#3883). Provide acabal.project.local
that overrides this and gets rid of the flag.cabal.project.somethingelse
, somehow gethaskell.nix
to include it?ghc-options: -Werror
in all your.cabal
files, guarded by a flag. Set this flag for all packages with module options.ghcOptions
module option to-Werror
for all your packages.At the moment I'm using option 4., but it's somewhat painful due to having to manually list all your packages. Both 3. and 4. would be eased if there was an easy way to set a module option for all the project packages in one go. Maybe there's a clever way to use the module system to do this?
The text was updated successfully, but these errors were encountered: