search

Vitalts / golangide

Automatically exported from code.google.com/p/golangide
0 stars 0 forks source link

Can not use gocode on x4,x5 version #28

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. extract gocode x86_64 version on linux
2. ln -s /usr/bin/gocode $GOROOT/bin (I read GOCODE.TXT, but...)
3. type "fmt."  only display "Println"

What is the expected output? What do you see instead?
1. "Println,Printf,...."

What version of the product are you using? On what operating system?
x5, x86_64 amd64 ArchLinux

Please provide any additional information below.
I don't know how to let godoc plugin work.
Suggest write some config method on README.TXT

Original issue reported on code.google.com by dlin...@gmail.com on 8 Jul 2011 at 6:55

GoogleCodeExporter commented 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

GoogleCodeExporter commented 8 years ago

Original comment by Visua...@gmail.com on 8 Jul 2011 at 8:31

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
The LiteBuild can work?

Original comment by Visua...@gmail.com on 8 Jul 2011 at 9:07

GoogleCodeExporter commented 8 years ago

Original comment by Visua...@gmail.com on 8 Jul 2011 at 9:08

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago

Original comment by Visua...@gmail.com on 15 Jul 2011 at 4:20