Why does go install creates an executable in binwindows_386?

  go, windows

As per the title, whenever I run go install relativepathtopackage it creates the binaries but places them in a folder called windows_386 in the $GOPATHbin folder. I purposely set GOARCH to the value 386. I’m running go 1.17.1 on Windows 10 Pro edition if this information is relevant. My theory is that I set GOARCH but in a "local" way, the "global" GOARCH is still amd64 and whenever I install packages with 386 architecture, it puts them in this subfolder. I haven’t been able to find any literature to confirm my suspicion though and would like some insight.

Source: Windows Questions

LEAVE A COMMENT