#Makefile vs runjs how to
#Makefile vs runjs install
#Makefile vs runjs software
#Makefile vs runjs code
#Makefile vs runjs windows

#Makefile vs runjs how to

When you run a command like go build, Go uses the current platform’s GOOS and GOARCH to determine how to build the binary.

However, Go can also cover less mainstream platforms like nacl, which represents Google’s Native Client. These cover the big three OS platforms: Linux, Windows, and macOS, which is based on the Darwin operating system and is thus called darwin. There are many platforms available with the go build command, but a majority of the time you’ll end up using linux, windows, or darwin as a value for GOOS. The GOARCH here would be 386, which stands for the Intel 80386 microprocessor. The key-value pair starts with the GOOS, which in this example would be linux, referring to the Linux OS. Let’s break down one of these combinations to understand what it means and how it works, using linux/386 as an example. This is pronounced “gore-ch”, and stands for Go Architecture. As before, these are all possible values for an environment variable: GOARCH. The second part, after the /, is the architecture. In Go, these operating systems are possible values for the environment variable GOOS, pronounced “goose”, which stands for Go Operating System.

The first part of the combination, before the /, is the operating system. This output is a set of key-value pairs separated by a /. Outputaix/ppc64 freebsd/amd64 linux/mipsle openbsd/386Īndroid/386 freebsd/arm linux/ppc64 openbsd/amd64Īndroid/amd64 illumos/amd64 linux/ppc64le openbsd/armĪndroid/arm js/wasm linux/s390x openbsd/arm64Īndroid/arm64 linux/386 nacl/386 plan9/386ĭarwin/386 linux/amd64 nacl/amd64p32 plan9/amd64ĭarwin/amd64 linux/arm nacl/arm plan9/armĭarwin/arm linux/arm64 netbsd/386 solaris/amd64ĭarwin/arm64 linux/mips netbsd/amd64 windows/386ĭragonfly/amd64 linux/mips64 netbsd/arm windows/amd64įreebsd/386 linux/mips64le netbsd/arm64 windows/arm You will receive an output similar to the following: To find this list of possible platforms, run the following: At the time of writing this tutorial, the current Go release is 1.13. This list can change with each new Go release, so the combinations discussed here might not be the same on another version of Go. The Go tooling has a command that can print a list of the possible platforms that Go can build on.

#Makefile vs runjs install

A Go workspace set up by following How To Install Go and Set Up a Local Programming Environment.īefore showing how to control the build process to build binaries for different platforms, let’s first inspect what kinds of platforms Go is capable of building for, and how Go references these platforms using the environment variables GOOS and GOARCH.To follow the example in this article, you will need: In this tutorial, you will put together a sample application that joins strings together into a filepath, create and selectively include platform-dependent snippets, and build binaries for multiple operating systems and system architectures on your own system, showing you how to use this powerful capability of the Go programming language.

#Makefile vs runjs code

By using environment variables and build tags, you can control which OS and architecture your final binary is built for, in addition to putting together a workflow that can quickly toggle the inclusion of platform-dependent code without changing your codebase. Go solves this problem by building support for multiple platforms directly into the go build tool, as well as the rest of the Go toolchain. You’d also need to keep your tooling in sync, in addition to other considerations that would add cost and make collaborative testing and distribution more difficult.

#Makefile vs runjs windows

In the past, for example, developing a program on Windows and deploying it to a Linux or a macOS machine would involve setting up build machines for each of the environments you wanted binaries for. However, this can be difficult when the platform you are using for development is different from the platform you want to deploy your program to. Since it is often slow or impossible to run a binary on a different OS/architecture platform, it is a common practice to build your final binary for many different platforms to maximize your program’s audience.

#Makefile vs runjs software

In software development, it is important to consider the operating system and underlying processor architecture that you would like to compile your binary for.