6 ms·

the whole gobin / gopath thing was annoying as a beginner: I just want to build this module and use that local module go build ./... Goes where ?

• coffeeindex 2y ago
  I believe it is recommended to not use gobin/gopath anymore. go test ./… tests all files in the project, so I assume build does something similar.
  • NAHWheatCracker 2y ago
    My experience with go build ./... is that it compiles everything but it doesn't make the binaries. > When compiling multiple packages or a single non-main package, build compiles the packages but discards the resulting object, serving only as a check that the packages can be built. From https://pkg.go.dev/cmd/go#hdr-Compile_packages_and_dependencies https://pkg.go.dev/cmd/go#hdr-Compile_packages_and_dependenc... A bit annoying when you want to build a bunch of executables, but it's not something I need often and it's easy to script.
    • arccy 2y ago
      go build -o some/dir/ ./... will actually output the binaries
      • NAHWheatCracker 2y ago
        Sick, I couldn't figure it out when I needed it so I just manually created a 20 line script to cd into each directory and go build.