I'm trying to use this for fairly complex projects like Kubernetes server components that are already pre-built.

Is it possible to make this work on compiled binaries like the blog post at https://science.raphael.poss.name/go-executable-size-visualization-with-d3.html explains?

I have a project created with gb pacakge manager and how can i execute the goweight command ?I see the following issue when i execute

# goweight
2019/04/04 18:12:17 exit status 1

I know this shouldn't happen, but I have a helper program that builds my project for different GOOS/GOARCH concurrently that resides within the project, along with the main.go.

If I run goweight, it exits with:

2019/04/03 10:58:28 exit status 2

Maybe there should be some way to define which .go files should be used to compile, or to exclude?

> go get github.com/jondot/goweight
package goweight/pkg: unrecognized import path "goweight/pkg" (import path does not begin with hostname)

I'm trying to use the tool, but it does not work and does not report why:

$ go get github.com/jondot/goweight
$ goweight
2021/08/31 11:00:22 exit status 2
$ goweight --version
dev (none)

My package imports a quite heavyweight library when certain build tag is specified. It would be nice to able to see how it contributes to the binary size.

Something like goweight -tags 'use_heavy_lib'

I am getting an error while trying this out on an example project. Any ideas?

1. $ git clone https://github.com/jondot/goweight
2. Jump to your project
3. $ goweight
4. See the error: operation not permitted

macOS - Go v1.15.5

I use this tool all the time. As well as a large number of gophers around the world. Therefore, I thought that reducing the number of dependencies would be a very useful step for the development of this project. That's why:

1. Faster installation, by reducing the number of network requests to get dependencies. On the cheapest VPS, the original goweight was installed in 31.402s, mine in 8.363s. This is almost 4x acceleration
2. Barely noticeable acceleration of startup by reducing the size of the executable file. It's almost imperceptible in a single run, but small wins add up to big wins when the tool is run hundreds of times every day by thousands of people around the world.
3. Reproducibility of builds and user safety. Over time, projects are abandoned, APIs change, github may be unavailable, and sometimes developer accounts are hacked to embed malicious functionality into library code. When we are not dependent on third-party solutions, we can be more confident that the project can be compiled without fear of "infection" and / or problems with the inaccessibility of something.

Binary size reduction on amd64 linux: 5848 B -> 3028 B

P.S. I would like to further develop and support goweight, which has not seen a release since May 2019. Assigning me as a maintainer will greatly help me improve the quality of the project and add more features to it. thanks

This project is most useful it seems for projects which produce large binaries and which have many dependencies. Such projects can take a long time to build. Thus, I suggest removing the -a flag from the build command. I do not know if it provides any value, because it's been there since the first commit. https://github.com/jondot/goweight/blob/624b44a7a73a54fe24a2061cca7030ff8855d488/pkg/goweight.go#L57

$ go help build
-a
    force rebuilding of packages that are already up-to-date.

First of all, thanks for sharing this tool, I found it very useful.

I've been analysing my binaries with this and I see that the sum of all sizes is much more than the final binary size. Is there any explanation to this? is there any way to know how much smaller a certain binary will be if I remove a dependency?

The tool is still very useful to focus on the biggest contributing dependencies, but sometimes I see a dependency of 6Mb for example, and after removing it completely I see the final binary only decreased 2Mb for example. I'd like to understand where the delta comes from.

The quick start instructions were correct, but this commit inverted them:

https://github.com/jondot/goweight/commit/746c1a5c7d649ec5d3faed6f9fe4d687b5c22a91

I think that commit should be reverted.