You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to siderolabs/talos#9429 the Windows binary for omnictl is currently not filled with properties. This is mostly informational though I do know Windows Installer looks at the file versions if it were used to distribute binaries. The file version field seems like the most useful and informative field to fill in. Those properties are currently blank.
Solution
Something like go-winres (https://github.com/tc-hib/go-winres) looks like it can be used with the Go ecosystem to fill in that manifest information.
Alternative Solutions
Investigation into tooling to support it also had led me to using windres from something like mingw to compile the manifest into a resource, but that's bringing in tooling outside the Go ecosystem so seems like a less favorable approach.
Notes
No response
The text was updated successfully, but these errors were encountered:
I got this proof of concept working as illustrated. The executable has an icon which I left as the default one go-winres produced and some basic executable properties are filled in though they likely need reviewed and tweaked. Build pipeline integration likely needs tweaked too. I'll make a branch/pull request with what I did.
Problem Description
Similar to siderolabs/talos#9429 the Windows binary for omnictl is currently not filled with properties. This is mostly informational though I do know Windows Installer looks at the file versions if it were used to distribute binaries. The file version field seems like the most useful and informative field to fill in. Those properties are currently blank.
Solution
Something like go-winres (https://github.com/tc-hib/go-winres) looks like it can be used with the Go ecosystem to fill in that manifest information.
Alternative Solutions
Investigation into tooling to support it also had led me to using windres from something like mingw to compile the manifest into a resource, but that's bringing in tooling outside the Go ecosystem so seems like a less favorable approach.
Notes
No response
The text was updated successfully, but these errors were encountered: