stack path #95
stack path #95
Comments
@snoyberg @chrisdone the implementation was not obvious to me, so I stubbed it out. I presume you two probably have the knowledge to trivially implement it from here, or give me some pointers on how to go about discovering these values? Also, I believe the code as written will create a project file if it doesn't exist, and that's probably not what we want it to do. But I don't see any other way to get a |
@DanBurton Reassigning to you actually. Please ping me on Slack to ask whatever questions you have about where to get this information. |
Also would be nice to know the path to built binaries. |
I'm just one person, but I'd really like to have this, at least for GHC. I tried to figure it out, but it's over my head. I'd be happy to take some pointers. |
For now I can just do |
Done. Passing over to @snoyberg to review. Here's how it looks:
|
LGTM. Can you update the ChangeLog about this? |
Done! |
Can we add an option that shows the path to the version of GHC that will actually be used to build? |
Yeah, that can be included. |
I closed an issue about this previously, but after discussing with @chrisdone we should implement it. Will have information about:
The text was updated successfully, but these errors were encountered: