#gopath

What is GOPATH and GOROOT in GoLang

Go tools expect a certain layout of the source code. GOROOT and GOPATH are environment variables that define this layout. These two are the most essential PATHs in GoLang. The go tool uses it to do the task in a better way. Now, we are going to take a look at what each one represents.

• GOPATH in Go Programming • GOROOT in GoLang • Modifying GOPATH and GOROOT

GOPATH in Go Programming

GOPATH is a…

Mac

Workspace Path

$ /Users/r2fresh/workspace/go/hello_project

LiteIDE 설정

먼저 Mac에 맞는 환경으로 셀렉트박스를 사용하여 아래와 같이 변경한다.

변경 후 아래의 이미지와 같은 버튼을 클릭한다.

설정 화면에서 자신의 workspace path경로를 입력한다.

Ubuntu

Workspace Path

$ /home/r2fresh-kt-ubuntu/workspace/go/hello_project

LiteIDE 설정

먼저 Ubuntu에 맞는 환경으로 셀렉트박스를 사용하여 아래와 같이 변경한다.

변경 후 아래의 이미지와 같은 버튼을 클릭한다.

설정 화면에서 자신의 workspace path경로를 입력한다.

Window

Workspace Path

E:\workspace\go\hello_project

LiteIDE 설정

먼저 Window에 맞는 환경으로 셀렉트박스를 사용하여 아래와 같이 변경한다.

변경 후 아래의 이미지와 같은 버튼을 클릭한다.

설정 화면에서 자신의 workspace path경로를 입력한다.

...which are defined in .zshrc (as I am using zsh). 

ln -s ~/.zshrc ~/.zprofile

I often switch off between distinct Go projects with distinct GOPATHs. While there were some bits and pieces of reasonable solutions on stack overflow, none fulfilled all of my requirements:

follows me around as my working directory changes

no need to remember a different name for the go toolchain meta-command

sets GOPATH properly even when the go command isn't running (this is important for the proper functioning of my vim setup, which relies heavily on the thoroughly excellent vim-go plugin)

allows for easy overriding if I need to explicitly set GOPATH from time to time.

This is what I added to my ~/.bash_profile:

export GOPATH="... a default path ..." function cd() { builtin cd $@ && export GOPATH="$( ( while [[ $PWD != / && $(basename $PWD) != go ]]; do cd .. done if [[ $PWD == / ]]; then echo $GOPATH else echo $PWD fi ))" }