Error paths should be relative to the current directory of the command that was invoked

[fatih]

I'm opening this issue after the conversation #63. After the fix #63, the error paths are relative to $PROJECT. This is a good step so tools can be built on top of error paths. However even better would be if the error paths are relative to current directory, just like the go tool does with go build, go instal etc..

Here is an example output of go tools (checkout the paths):

Here is how gb outputs the paths:

The advantages how having the paths relative to current directory would be the reusage of current tooling around the go tools. Of course the arguments that are passed to gb build and go build are also different.

[davecheney]

I haven't forgotten about it. I'm planning to tackle this with the cgo work #92.