-
Notifications
You must be signed in to change notification settings - Fork 63
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 use hie with custom-setup? #352
Comments
Hi! This seems to happen because we run
(I am not checking for validity, or how many times this will rebuild now stuff because it re-touches the generated file). I also used a cabal cradle: cradle:
cabal: but that was mainly because I am more comfortable understanding cabal shenanigans. However, it might be possible that this doesn't work for stack: commercialhaskell/stack#4315 We overall might have a better experience, if we make use of a proper cabal API as we are implementing here: haskell/cabal#7500. And then, we will have to teach stack about it. |
Thank you very much for the suggestion. and also for the links. They give good insight in all the hard work being done for Haskell tooling. Thanks! |
In a project I use, we have a build-type: Custom. During executing Setup.hs, a new .hs file is being generated.
Currently, I use the HSL setup with VSCode. That works great, except that before it is working, we have to manually build the project, so that the generated file can be found.
Is there support for projects with a Custom build-type?
Project I am talking about: https://github.com/AmpersandTarski/Ampersand
The actual setup is done using .devcontainer
The text was updated successfully, but these errors were encountered: