Setting up Goland to compile plugins on Windows

Hi, I am just starting out using Nakama and I’ve been struggling trying to compile plugins on Windows, since Go does not support -buildmode=plugin on this OS. So I was trying to make the workflow better by setting up Goland for syntax highlighting and stuff.

But I could not make Go cross-compile correctly, I tried setting the GOOS environment variable to ‘linux’, but I think it’s not enough because it says:

C:\Go\pkg\tool\windows_amd64\link.exe: running gcc failed: exec: "gcc": executable file not found in %PATH%

So I think that I need to use linux toolchain to build it correctly, but no idea how to install it for Windows, asking for help.

As a workaround, I just go to WSL and compile it from there, but eh, I want it to be a one-button job :slight_smile:

Hey @BeLuckyDaf did you resolve you questions about using Go runtime plugins with Nakama?

Well, yeah, I’m just using WSL and a simple shell script to automate building modules.

1 Like

@BeLuckyDaf can you share the steps you use as a workflow as I think it will help other Windows developers. Thanks :pray:


  1. Install Visual Studio Code to use with WSL:
    a. Install the Remote WSL extension:
    b. Probably Golang extension wouldn’t hurt too:
  2. Install WSL:
  3. Install a distro for WSL from Microsoft Store, e.g. Ubuntu
  4. Install the correct version of Go into WSL:
  5. Install CockroachDB:

Setting up Nakama & Cockroach

  1. Make a directory for the local Nakama server
mkdir nakama-server
cd nakama-server
  1. Download and extract Nakama binary
tar -xzvf nakama-2.12.0-linux-amd64.tar.gz
# here you might want to remove everything except for the binary itself
  1. Create a directory for the local database & start it there
mkdir db
cd db
cockroach start-single-node --insecure
# now go for another terminal, leave the db working here
  1. Start Nakama and make sure everything is fine
./nakama migrate up
# if you see that everything went well, shut it down for now

Setting up the project

  1. Create your go.mod file. This is what it would look like if MODULENAME is the name of your server module

go 1.14

require ( v1.3.5 v1.5.1

Now, it’s worth mentioning that vscode would probably try to suggest you to upgrade the version of protobuf. Don’t, or if you did, get it back to 1.3.5 (at this point).

  1. Optionally, write a shell script for automatic module building and launching Nakama with it. This is super useful, because you’re gonna rebuild hundreds of times during the development and this is an easy and super quick way to do it, instead of manually copying and pasting your .so module.
export NAKAMA_RUNTIME_PATH=<path-to-where-you-want-you-data-stored>
export NAKAMA_PATH=<path-to-directory-with-nakama-executable>
export MY_NAKAMA_MODULE_NAME=<nakama-module-name>

# e.g. in my case it is
# export NAKAMA_RUNTIME_PATH=/home/beluc/nakama-server/
# export NAKAMA_PATH=/home/beluc/nakama-server/
# export MY_NAKAMA_MODULE_NAME=spacebattle

if (go build -buildmode=plugin -trimpath -o $NAKAMA_RUNTIME_PATH/data/modules/$ ; then 
    $NAKAMA_PATH/nakama migrate up
    $NAKAMA_PATH/nakama -runtime.path $NAKAMA_RUNTIME_PATH


Try it out on Heroic Labs’ sample Nakama module: