Hi, I'm trying to optimize the build of my app. Our build times have crept up to ~60s as we've added more dependencies and it's starting to become a problem.
The primary problem seems to be that we're building in a container, so we're losing the $GOPATH/pkg cache of build artefacts between builds. However, even if I bind the same directory to that location for each run, it doesn't seem to help. The artefacts (.a files) get built and added to that directory but the following build seems to ignore them and rebuild them anyway. If I do two builds in the same container then it does pick up the artefacts. Likewise, if I build outside the container it seems to work as expected. I feel like there's something I'm missing. Please can you help me understand how "go install" determines the freshness of artefacts and why they might not be being used? I tried running with -x but I can't see any info about freshness (but then I'm not sure what I'm looking for in that output). Thanks, -Shaun -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
