goxc cannot handle multiple entries in $GOPATH about goxc

[laher]

Hi Sanjay, thanks for the heads-up. It's an important point!
I'll fit this into the next release this weekend.

• Good call about using go/build. It doesn't expose as much as I'd like - e.g. build.Context has a private method 'gopath()', and I don't want to call build.DefaultContext.Import(...) at this stage. For now I'll borrow the logic from Context.gopath(), and look into using Import in the future, (it could be useful for lots of stuff).
• I'll also get goxc to attempt to select the relevant path element based on 'working directory' (and if not then fall back to the first element, as you suggest).

In the meantime please use GOPATH=/your/path goxc.

Thanks, I'll keep you posted.

[laher]

Or , also for now, please use goxc -d=/your/path

[laher]

OK, latest version includes this fix. Please test.

NOTE: the latest version v0.5.0 is a major change. This is especially significant if you have been using a .goxc.json config file. Otherwise, just be aware that the default operation of goxc includes running go test and go vet on your code.

The executable should guide you in case your config is affected. Please read up on the changes (e.g. start on the README.md and follow links through to the wiki). goxc -h also displays more info than before.

Hope this helps

[balasanjay]

Tested locally. Works well.

Thanks.