Skip to content

Go#

Installation on Windows#

winget install -e --id=GoLang.Go

General#

Installing Tool Dependencies#

[!WARNING]
New versions of go have native support for this!

  • #BUG: this is a bit of a hack, but it works. It allows us to have a "self
    contained" codebase, there are not (a lot of) external tools required
    for this to work.

  • Create a file tools.go

// This comment is here so that the "normal" build process ignores it.
// To install these dependencies run:
//
// `go get -tags tools .`
//
// or simply
//
// `go mod tidy`

//go:build tools

// This allows us to have a "self contained" codebase,
// there are not (a lot of) external tools required for this to work.

//go:generate go install "google.golang.org/grpc/cmd/protoc-gen-go-grpc@latest"
//go:generate go install "google.golang.org/protobuf/cmd/protoc-gen-go@latest"

package main

import (
  _ "google.golang.org/grpc/cmd/protoc-gen-go-grpc"
  _ "google.golang.org/protobuf/cmd/protoc-gen-go"
)
  • Run the following command
go mod tidy
go get -tags tools ./...
go generate -tags tools

Getting a specific dependency version#

Source

You can get a specific version of a dependency module by specifying
its version in the go get command. The command updates the require
directive in your go.mod file (though you can also update that
manually).

You might want to do this if:

You want to get a specific pre-release version of a module to try out.
You\'ve discovered that the version you\'re currently requiring isn\'t
working for you, so you want to get a version you know you can rely
on. You want to upgrade or downgrade a module you\'re already
requiring. Here are examples for using the go get command:

To get a specific numbered version, append the module path with an @
sign followed by the version you want:

go get example.com/theirmodule@v1.3.4

To get the latest version, append the module path with \@latest:

go get example.com/theirmodule@latest

The following go.mod file require directive example (see the
go.mod reference for more)
illustrates how to require a specific version number:

  • #BUG: find out if go.mod lexer is available
# gomod
require example.com/theirmodule v1.3.4

Discovering available updates#

Source:

You can check to see if there are newer versions of dependencies
you\'re already using in your current module. Use the
go list command to display a list
of your module\'s dependencies, along with the latest version
available for that module. Once you\'ve discovered available upgrades,
you can try them out with your code to decide whether or not to
upgrade to new versions. For more about the
go list command, see
go list -m.

Here are a couple of examples.

List all of the modules that are dependencies of your current module,
along with the latest version available for each:

go list -m -u all

Display the latest version available for a specific module:

go list -m -u example.com/theirmodule

gRPC#

[grpc/note.foam.md#Required Tools]: <../grpc/note.foam.md#Required Tools> "gRPC"

[git.foam.md#Using BitBucket Server/Datacenter Git]: "Git"