Always builds with $HOME/.stack as stack root
See original GitHub issueHi, I recently moved my stack root to another drive because it was getting too big. I set the environment variable $STACK_ROOT
to the new locations and when I run stack build
everything works fine.
However, when I open the project in intellij, it starts building dependencies with the default stack root. Even when I --stack-root /home/stack
to the stack arguments in the settings, it does not use my new root.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
User's guide (introductory) - The Haskell Tool Stack
To build your project, Stack uses a project-level configuration file, named stack.yaml , in the root directory of your project as a sort...
Read more >stack build shows "No directory could be located ..." inside ...
I'm building a project inside a docker container, with this cmd: stack --stack-root /app/build/stack-root/ --work-dir build/work-dir/ build ...
Read more >Caching stack databases between builds in Gitlab CI
Am I correct in thinking that snapshots always are stored in STACK_ROOT ? Is there a way to pre-fetch a specific snapshot, similar...
Read more >New in-depth guide to stack - FP Complete
The stack build tool is a cross-platform program for developing Haskell projects. It is aimed at Haskellers both new and experienced.
Read more >Card navigation | Apps Script - Google Developers
This first card is a root card. Your add-on can create additional non-contextual cards and push them onto the stack (the blue "pushed...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can confirm! Thank you 😃
Should be fixed in beta75