Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Absolute paths #1348
Compiler messages will only display the relative path to source files from their respective packages (except in one case). For instance, if I check out the stack-ide project and update
This is, of course, relative to the
One workaround is to
Is there a way to have stack reliably produce absolute paths? If it could at least report out the absolute path to the package it is building before reporting messages, that would give the consumer process a consistent and efficient way to determine where the source file resides.
Some additional context - I am working on providing users of HaskForce the ability to build their projects with stack. It is consuming output from
There may be a better or simpler way to determine the absolute paths to the source files, so I am open to any solutions.
This looks like a duplicate of #1259, which is fixed in master. Can you
On Sun, Nov 15, 2015 at 6:28 PM Cary Robbins email@example.com
Thanks, I was able to reproduce this using the stack-ide repo as well. The problems appears to be that the paths output by GHC are canonicalized to absolute paths when Stack is directly passing GHC's output to the console, but not when it dumps the log after a build failure. That means if you're only building a single package, the paths do get canonicalized (e.g. try