Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Btcd.exe leaves the description field blank when shown in Process Explorer(WinXP 32 SP3). #53

Open
typeless opened this issue Nov 28, 2013 · 6 comments

Comments

@typeless
Copy link

No description provided.

@davecgh
Copy link
Member

davecgh commented Nov 28, 2013

Go programs don't have the standard VERSIONINFO resource that Visual Studio projects have which is what provides that information. There are ways to get this information into the executable via external utilities, but honestly it will be extremely low priority as it doesn't have any bearing on the actual functionality of the application.

I'll leave the ticket open as something to tackle when the much higher priority issues are resolved.

@typeless
Copy link
Author

I thought it's just something missing in configuration or whatever. Such being the case, fully appreciated.

@dajohi
Copy link
Member

dajohi commented Mar 20, 2014

@davecgh
Copy link
Member

davecgh commented Mar 21, 2014

I have a local resource.rc file which handles this, but the issue is actually building the .syso. We obviously don't want to require mingw + windres to build the executable on Windows.

Also, the .rc file has version information in it, so ideally it would be populated at build time from the information in version.go which would require some type of pre-processing step.

I suspect we can incorporate this into our MSI build process without much hassle, but I don't forsee this working for users building from source without them going through extra hoops.

gsalgado pushed a commit to gsalgado/btcd that referenced this issue Jul 29, 2014
davecgh pushed a commit to davecgh/btcd that referenced this issue Oct 11, 2017
Go 1.8 is out and by policy we only support the latest two Go releases.
@jakesylvestre
Copy link
Collaborator

Anyone know if this is still an issue? Seeing as this is tagged as windows xp/there's no mentions since I'd guess this got fixed in a newer version but have no way to verify. @davecgh any ideas?

@davecgh
Copy link
Member

davecgh commented Aug 28, 2020

It's still the case, but realistically it's been 7 years and nobody really seems to care too much.

That said, there is tool for this nowadays that could be used here. It generates the necessary VERSIONINFO resource information in a .syso COFF file that the Go linker will automatically link into the binary if it's alongside the file that contains the main func thus producing the desired result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants