How to Build Multiple Binary Packages with a Script?
Nov 03, 2024 am 10:45 AMBuilding Multiple Binary Packages: An Alternative Approach
While the recommended approach to building multiple binaries involves organizing packages within a top-level cmd folder, this does not always suffice. Instead, an alternative solution is to employ a script that iterates over the individual packages.
cd $GOPATH/someProject for CMD in `ls cmd`; do go build ./cmd/$CMD done
This script efficiently constructs binaries for each package within the cmd directory, resulting in an output similar to this:
[root@node1 test]# ls $GOPATH/someProject bin1 bin2 cmd
This approach offers a viable alternative to the default advice of utilizing a cmd folder structure. By implementing a script to automate the build process, you can easily build multiple binaries in a single step and achieve the desired results.
Example Projects to Reference:
- Grafana: https://github.com/grafana/grafana/blob/master/build.go
- Torus: https://github.com/coreos/torus/blob/master/Makefile
- Caddy: https://github.com/mholt/caddy/blob/master/dist/automate.go
The above is the detailed content of How to Build Multiple Binary Packages with a Script?. For more information, please follow other related articles on the PHP Chinese website!

Hot Article

Hot tools Tags

Hot Article

Hot Article Tags

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Go language pack import: What is the difference between underscore and without underscore?

How to implement short-term information transfer between pages in the Beego framework?

How do I write mock objects and stubs for testing in Go?

How to convert MySQL query result List into a custom structure slice in Go language?

How can I define custom type constraints for generics in Go?

How can I use tracing tools to understand the execution flow of my Go applications?

How to write files in Go language conveniently?
