分叉存储库上的“ go build”问题

Question

I build a binary file for a GitHub repo (go code), which works fine. no issues. I forked that repo, and modified a single line in the HTML file that has nothing to do with GO code, built the binary file for the new forked repo but the binary it generates refers to the original repo code, can't understand why.

I even cleaned all the code using go clean -i all command and manually removed all the installed code, binary files from $home/go/bin and the repo directory, but it still refers to the original repo code instead of new forked code.

---

Based on the solution suggested by Tobias, I performed the following steps:

After that, I executed go build in that repo directory, but the new binary file still refers to the old code. I even removed the old binary file and generated a new one.

Answer 1

SOLVED

At first I thought it was problem with a FORK (which is a common problem experienced with fork of Go language repo's), but it turns out, it was Repo specific problem. One of the dependent libraries had to be reinstalled for the forked repo to work, which was not mentioned in the Original repo docs. Finally, this link helped: https://github.com/inconshreveable/ngrok/issues/181#issuecomment-65646229, the problem was not generic but repo specific I followed the below steps from above link to resolve the dependency on go-bindata

go get github.com/jteeuwen/go-bindata
cd $GOPATH/src/github.com/jteeuwen/go-bindata/go-bindata
go build