ohh, then you can look into *windres* which comes with mingw.
It can create a C object file (from a .rc file that then references the
manifest) which you then should be able to link into using the apporiate
flags through cgo
On Friday, 18 September 2020 at 6:19:02 am UTC+8 aro...@gmail.com wrot
Thanks! I'll look more into that. Unfortunately, we're not building on a
windows machine. :-( Might still be able to make something work, though.
On Thursday, September 17, 2020 at 9:26:25 AM UTC-6 Alex wrote:
> Yeah looks like *mt.exe* would be the most painless method assuming it
> works.
>
Yeah looks like *mt.exe* would be the most painless method assuming it
works.
On Thursday, 17 September 2020 at 11:14:36 pm UTC+8 aro...@gmail.com wrote:
> Thanks for the reply. Yes, I want to override the manifest for a
> particular build of the binary.
>
> I have two modules:
> 1. foo.com/rep
Thanks for the reply. Yes, I want to override the manifest for a particular
build of the binary.
I have two modules:
1. foo.com/repo1 which contains foo.com/repo1/cmd/the-binary
2. foo.com/repo2 which will build and package the-binary with specific
version and manifest information. I'd like to g
> Is there a way to force the go linker to include the local manifest file?
A syso file *is* the way.
> Or somehow inject the manifest into a built exe?
Readup on *mt.exe*, I haven't used it on go programs but it might work.
https://docs.microsoft.com/en-us/cpp/build/how-to-embed-a-manifest-insi
