-
Notifications
You must be signed in to change notification settings - Fork 206
HIE gives "could not execute: <some preprocessor exe>" #1500
Comments
No, you have to have |
The proper solution here is to execute |
While this is true, I dont think that this is really a viable solution for some users. E.g. we endorse the hie-wrapper, which can currently not handle this at all. But maybe we can fix that. |
I think it is important that hie is able to build based on whatever environment the project is using. If it uses |
@fendor, @mpickering, @alanz, thank you all for the answers! (FYI, even though I had installed tasty-discover globally and made it work, I posted this issue because I don't think global installation is an optimal solution) |
Oh, I see. It's hard to change the behaviour since it is the behaviour of GHC library. |
Exactly. We would have to manipulate the path ourselves, which is doable, but definitely postponed for now. |
In stack cradle (more specifically, I use multi-cradle with stack), if a preprocessor executable is installed only locally but not globally, HIE says
could not execute: <the name of the preprocessor>
.For my case, I use
tasty-discover
, and mypackage.yaml
specify it as a dependency like this,but HIE emits
could not execute: tasty-discover
.Maybe this is related to mpickering#60 and will be solved by #1496, but I am not sure.
The text was updated successfully, but these errors were encountered: