I’m trying to embed windows manifest information into an exe. I’ve generated the resource.syso file using goversioninfo and it works fine when that file is in the target package. But now I want to do something slightly different: I want to use go build module/package/cmd/binary with a locally-generated resource.syso. Is there a way to force the go linker to include the local manifest file? Or somehow inject the manifest into a built exe? Currently I have two workarounds that I’m trying to avoid:
1. The main package of the target binary is incredibly thin and I duplicate the main package locally and compile with the generated syso file. 2. I can use modcacherw to allow modifications of the imported module package and modify the source folder of the binary and inject the syso file. Any way to make go build just link in the file? - Augusto -- 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/0584be92-cd6f-4945-a722-7e62bf8b0561n%40googlegroups.com.
