Closed GoogleCodeExporter closed 8 years ago
GolandCode and GolangDoc plugin depends of LiteBuild -> BuildEnv
Load *.go file and use switch env "Linux64"
LiteIDE->Option->LiteBuild-> go/linux64.env
PATH=$HOME/go/bin:$PATH
GOROOT=$HOME/go
GOBIN=$HOME/go/bin
GOARCH=amd64
GOOS=linux
Original comment by Visua...@gmail.com
on 8 Jul 2011 at 8:26
Original comment by Visua...@gmail.com
on 8 Jul 2011 at 8:31
It can not work. I've set and close then reopen.
PATH=/opt/go/bin:$HOME/liteide/bin:$PATH
GOROOT=/opt/go
GOBIN=/opt/go/bin
GOARCH=amd64
GOOS=linux
Intead of use these GOXXX environment, I suggest ref /opt/go/test/run.
Use following line as launch script on linux env, it will get the result from
GOROOT.
eval $(gomake --no-print-directory -f $GOROOT/src/Make.inc go-env)
Original comment by dlin...@gmail.com
on 8 Jul 2011 at 8:40
The LiteBuild can work?
Original comment by Visua...@gmail.com
on 8 Jul 2011 at 9:07
Original comment by Visua...@gmail.com
on 8 Jul 2011 at 9:08
How to detect what's config file I'm using?
How to show what command liteide will run?
How to enter debug/verbose mode to show out information on console?
I've follow your setting, and more, I modified the linux64-user.xml.
Original comment by dlin...@gmail.com
on 8 Jul 2011 at 10:00
Pardon for the intromission but i have de same problem, gocode not work in
Liteide.
I have the same configuration . Linux 64 bits and I was adjusted the settings
following your instructions but not work.
Any idea?
Original comment by jvtech...@gmail.com
on 8 Jul 2011 at 5:01
[deleted comment]
[deleted comment]
It is suggested to call by "gocode -s -sock=tcp".
I just asked gocode's author nsf, and he said:
"I'm sure it works properly. I can imagine only single reason why it happens:
gocode process was killed and the file it was using to represent the unix
socket is still there in /tmp, therefore client cannot connect to a dead
socket. So, just delete it manually.
Also if unix socket really doesn't work it is possible to change it by running
gocode client/server with "-sock" flag.
E.g. `gocode -s -sock=tcp`
I really don't want to change the default socket type to tcp on *nix machines."
Original comment by dlin...@gmail.com
on 11 Jul 2011 at 2:03
test gocode
>gocode status
dial unix /tmp/acrserver.xxx: connection refused (xxx = $USER)
>rm /tmp/acrserver.xxx
gocode is ok.
Original comment by Visua...@gmail.com
on 15 Jul 2011 at 4:17
Original comment by Visua...@gmail.com
on 15 Jul 2011 at 4:20
Original issue reported on code.google.com by
dlin...@gmail.com
on 8 Jul 2011 at 6:55