I have a makefile where upon a new go binary being built, it builds some other stuff that is not go related.
The go binary is unconditionally built with a FORCE prerequisite, so the go build command always runs, but that command always updates the output binary, which leads to downstream being unnecessarily built. Is there a way to tell go not to touch the output file if it builds purely from the cache? Currently it prevents me from using a makefile, and I don't really feel like sidestepping go's cache system by manually listing all go files and have the makefile functions as a cache, besides, it's really difficult to correctly list dependencies if the module is big and the binary being built only depends on a subset. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/edca0a5c-7ed0-4631-900c-9df818b41263%40googlegroups.com.
