Go/Installing - Revision history

Admin: /* Paths */

2018-12-19T01:29:12Z

Paths

← Older revision		Revision as of 01:29, 19 December 2018
Line 50:		Line 50:
	* PATH - update PATH to include the binary folder of both GOROOT and GOPATH		* PATH - update PATH to include the binary folder of both GOROOT and GOPATH

	For example, if Go were installed to the home directory in <code>go/</code> and <code>work/</code>, these lines would be added to the user's <code>.profile</code> file:		For example, if Go were installed to the home directory in <code>~/go/</code>, and the user kept Go projects in <code>~/work/</code>, these lines would be added to the user's <code>.profile</code> file:

	<pre>		<pre>

Admin: /* Flags */

2018-12-07T17:23:10Z

Flags

← Older revision		Revision as of 17:23, 7 December 2018
Line 107:		Line 107:
	Hello, World!		Hello, World!
	</pre>		</pre>

			Also see https://golang.org/doc/code.html (section: Your First Program)

	=Flags=		=Flags=

	{{GoFlag}}		{{GoFlag}}

Admin: /* Testing */

2018-12-07T04:33:12Z

Testing

← Older revision		Revision as of 04:33, 7 December 2018
Line 97:		Line 97:

	<pre>		<pre>
	which hello		$ which hello
			/home/user/work/bin/hello
	</pre>		</pre>

Line 106:		Line 107:
	Hello, World!		Hello, World!
	</pre>		</pre>


	=Flags=		=Flags=

	{{GoFlag}}		{{GoFlag}}

Admin at 04:30, 7 December 2018

2018-12-07T04:30:40Z

← Older revision		Revision as of 04:30, 7 December 2018
Line 106:		Line 106:
	Hello, World!		Hello, World!
	</pre>		</pre>


			=Flags=

			{{GoFlag}}

Admin: /* Testing */

2018-12-07T04:30:02Z

Testing

← Older revision		Revision as of 04:30, 7 December 2018
Line 62:		Line 62:
	Now that Go is installed and the paths are set for your server, you can test to ensure that Go is working as expected.		Now that Go is installed and the paths are set for your server, you can test to ensure that Go is working as expected.

	Create ~~a new directory for your~~ Go workspace, which is where Go will build its files:		Create Go workspace, which is where Go will build its files:

	mkdir $HOME/work		mkdir $HOME/work

	~~Then, create~~ a directory hierarchy ~~in this folder in order for you to create your test program file~~. ~~We’ll use the directory~~ my_project as an example.		Create a directory hierarchy. Use <code>my_project</code> as an example top-level directory for this example, and a hello subfolder:

	mkdir -p work/src/my_project/hello		mkdir -p work/src/my_project/hello

	~~Next, you can~~ create a traditional ~~"Hello World"~~ Go file.		Now create a traditional hello world Go file:

	~~nano~~ ~/work/src/my_project/hello/hello.go		vim ~/work/src/my_project/hello/hello.go

	~~Inside your editor, paste~~ the code ~~below, which uses the main Go packages, imports the formatted IO content component, and sets a new function to print "Hello, World" when run.~~		Edit this file and add the contents:
	hello.go
			'''<code>hello.go</code>:'''

	<pre>		<pre>
Line 87:		Line 88:
	</pre>		</pre>

	~~This~~ program ~~will print "~~Hello, World!~~" if it successfully runs, which will indicate that Go programs are compiling correctly. Save and close the file, then compile it by invoking the Go command install:~~		Now run this via:

			<pre>
			go install my_project/hello
			</pre>

			You should see your Go program when you type which hello:

			<pre>
			which hello
			</pre>

			Now test:

			<pre>
			$ hello
			Hello, World!
			</pre>

Admin: /* Paths */

2018-12-07T04:26:34Z

Paths

← Older revision		Revision as of 04:26, 7 December 2018
Line 57:		Line 57:
	export PATH=$PATH:$GOROOT/bin:$GOPATH/bin		export PATH=$PATH:$GOROOT/bin:$GOPATH/bin
	</pre>		</pre>

			=Testing=

			Now that Go is installed and the paths are set for your server, you can test to ensure that Go is working as expected.

			Create a new directory for your Go workspace, which is where Go will build its files:

			mkdir $HOME/work

			Then, create a directory hierarchy in this folder in order for you to create your test program file. We’ll use the directory my_project as an example.

			mkdir -p work/src/my_project/hello

			Next, you can create a traditional "Hello World" Go file.

			nano ~/work/src/my_project/hello/hello.go

			Inside your editor, paste the code below, which uses the main Go packages, imports the formatted IO content component, and sets a new function to print "Hello, World" when run.
			hello.go

			<pre>
			package main

			import "fmt"

			func main() {
			fmt.Printf("Hello, World!\n")
			}
			</pre>

			This program will print "Hello, World!" if it successfully runs, which will indicate that Go programs are compiling correctly. Save and close the file, then compile it by invoking the Go command install:

Admin: /* Paths */

2018-12-07T04:25:36Z

Paths

← Older revision		Revision as of 04:25, 7 December 2018
Line 46:		Line 46:
	Edit your <code>.profile</code> to make the following changes to your environment variables:		Edit your <code>.profile</code> to make the following changes to your environment variables:

	* GOROOT - (by default, this is /usr/local, ~~not necessary to~~ change) the location of your Go tree		* GOROOT - (by default, this is /usr/local, only change if you are using a different location) the location of your Go tree
	* GOPATH - this is a list of paths in which Go code, packages, objects, and executables are stored		* GOPATH - this is a list of paths in which Go code, packages, objects, and executables are stored
	* PATH - update PATH to include the binary folder of both GOROOT and GOPATH		* PATH - update PATH to include the binary folder of both GOROOT and GOPATH

Admin: /* Paths */

2018-12-07T00:34:25Z

Paths

← Older revision		Revision as of 00:34, 7 December 2018
Line 46:		Line 46:
	Edit your <code>.profile</code> to make the following changes to your environment variables:		Edit your <code>.profile</code> to make the following changes to your environment variables:

	* GOROOT - this is /usr/local ~~by default~~, the location of your Go tree		* GOROOT - (by default, this is /usr/local, not necessary to change) the location of your Go tree
	* GOPATH - this is a list of paths in which Go code, packages, objects, and executables are stored		* GOPATH - this is a list of paths in which Go code, packages, objects, and executables are stored
	* PATH - update PATH to include the binary folder of both GOROOT and GOPATH		* PATH - update PATH to include the binary folder of both GOROOT and GOPATH

	For example, if Go were installed to the home directory in <code>go/</code> and <code>work/</code>, these lines would be added to the user's .profile file:		For example, if Go were installed to the home directory in <code>go/</code> and <code>work/</code>, these lines would be added to the user's <code>.profile</code> file:

	<pre>		<pre>

Admin: Created page with "=Installing Go= ==Linux== Visit the Go downloads page: https://golang.org/dl Get the URL for the latest version of Go Download go:

 curl -O https://dl.google.com/go/..."

2018-12-07T00:33:24Z

Created page with "=Installing Go= ==Linux== Visit the Go downloads page: https://golang.org/dl Get the URL for the latest version of Go Download go: <pre> curl -O https://dl.google.com/go/..."

New page

=Installing Go=

==Linux==

Visit the Go downloads page: https://golang.org/dl

Get the URL for the latest version of Go

Download go:

<pre>
curl -O https://dl.google.com/go/go1.11.2.linux-amd64.tar.gz
</pre>

Verify checksum:

<pre>
sha256sum go*.tar.gz
</pre>

Now you're ready to install Go:

<pre>
tar xvf go*.tar.gz

sudo chown -R root:root ./go

sudo mv go /usr/local
</pre>

==Mac==

<pre>
brew install go
brew upgrade go
</pre>

==Goenv==

Following the successful model of pyenv, you can use goenv to set up and manage various side-by-side versions of Go.

Link: https://github.com/syndbg/goenv

=Paths=

Edit your <code>.profile</code> to make the following changes to your environment variables:

* GOROOT - this is /usr/local by default, the location of your Go tree
* GOPATH - this is a list of paths in which Go code, packages, objects, and executables are stored
* PATH - update PATH to include the binary folder of both GOROOT and GOPATH

For example, if Go were installed to the home directory in <code>go/</code> and <code>work/</code>, these lines would be added to the user's .profile file:

<pre>
export GOROOT=$HOME/go
export GOPATH=$HOME/work
export PATH=$PATH:$GOROOT/bin:$GOPATH/bin
</pre>