-
Notifications
You must be signed in to change notification settings - Fork 689
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
Allow user configurable command line options for build tools #1223
Comments
This would be nice, and would give the package developer a bit of control back over how the tools get run. |
Probably best solved via tool-specific pragmas. |
With regard to this comment:
This is not strictly true, you can set |
I just noticed, one can workaround this also via a project-
Not sure though if it's a good idea to include that file via (It may actually be a good idea to reject package uploads to Hackage which contain a top-level |
I just run into the same issue. This seems like a fairly obvious and trivial feature, and this ticket is over 5 years old. Are there any technical difficulties, or are we just lacking manpower? |
Patches definitely welcome. |
I found that Alex has an "encoding" directive, so one can do:
instead of passing |
There is currently no mechanism to control how tools like
happy
are invoked by cabal. Other tools that would be nice to control over include (but not limited to),hsc2hs
,c2hs
, andalex
.A simple option would be to add a field
happy-options:
to the cabal file format. An even better solution would be for the mechanism to allow the options to be per module. An even better solution would make the addition of tools with options into a generic configurable option so that new build tools can be added without modifying cabal.The text was updated successfully, but these errors were encountered: