duan5731
2016-08-26 06:58
浏览 131
已采纳

Golang-为什么在类似计算机上进行编译会导致二进制文件大小明显不同?

I have a gorilla/mux based web service written in Golang. I've observed that the exact same code produces a binary of size more than 10 MB on my Windows 10 Pro Machine while its about 7 MB on my colleague's Windows 10 Pro Machine. On yet another colleague's MacBook Pro running OS X Yosemite, the binary is just a bit over 11 MB in size. What does this binary actually contain?!

图片转代码服务由CSDN问答提供 功能建议

我有一个用Golang编写的基于大猩猩/ mux的Web服务。 我观察到生成的代码完全相同 Windows 10专业版计算机上的二进制文件大小超过10 MB,而同事的Windows 10专业版计算机上的文件大小约为7 MB。 在另一位运行OS X Yosemite的同事的MacBook Pro上,该二进制文件的大小仅略超过11 MB 。 此二进制文件实际上包含什么?!

  • 写回答
  • 好问题 提建议
  • 追加酬金
  • 关注问题
  • 邀请回答

1条回答 默认 最新

  • douzhang1955 2016-08-26 07:12
    最佳回答

    It may be due to different architectures (GOARCH env variable). Run go env to verify. Compiled binary to 386 and to amd64 differs significantly (compiled to amd64 is significantly bigger), but it should be close if the architecture is the same with different OS.

    Also the Go version itself matters a lot, Go 1.7 reduced the compiled binary size. See blog post Smaller Go 1.7 binaries for details.

    Also I assume it's the same, but whether debug info is excluded can reduce the compiled binary size significantly.

    评论
    解决 无用
    打赏 举报

相关推荐 更多相似问题