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

Manifest does not work #29

Closed
ghost opened this issue Apr 16, 2020 · 5 comments
Closed

Manifest does not work #29

ghost opened this issue Apr 16, 2020 · 5 comments

Comments

@ghost
Copy link

ghost commented Apr 16, 2020

App dir "my_app/"
--- main.go
--- myicon.ico
--- main.manifest

Manifest

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
    <assemblyIdentity type="win32" version="1.0.0.0" processorArchitecture="ia64" name="Company.Department.MyApp"/>
</assembly>

syso
I generate the .syso file using the command:
rsrc -ico myicon.ico -manifest main.manifest -o main.syso

Build
I build the exe using the command:
go build

Issue
The exe is compiled and works. The exe icon is shown. But when I look at the properties of the executable, it is the default. The name is not set, for example.
How to fix this?

go1.14.2.windows-amd64
rsrc - latest version

@fcharlie
Copy link

Is it because the processor architecture ia64 is not supported? try to change to the following settings:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
    <assemblyIdentity type="win32" version="1.0.0.0" processorArchitecture="*" name="Company.Department.MyApp"/>
</assembly>

@ghost
Copy link
Author

ghost commented Apr 17, 2020

fcharlie commented:
Is it because the processor architecture ia64 is not supported? try to change to the following settings..

I have tried. The product name and version are still empty.

@akavel
Copy link
Owner

akavel commented Apr 17, 2020

I'm afraid I personally probably don't know enough about this to help you. The only things that come to my mind are:

  1. I think (though I may be wrong) that the "version" showed by Windows on an .exe file doesn't actually come from manifest file, but from data stored in binary in a similar way as .ico files are stored - see Any chance of supporting VERSION_INFO in addition to app.manifest? #10. I unfortunately currently lack capacity to work on rsrc anymore to add this; to verify if this works for you, you could consider trying https://github.com/josephspurrier/goversioninfo
  2. Other than that, I'm confused as to what processor architecture you're using. You mention amd64 version of Go - does it show up as so when you run go env GOARCH? If yes, for .syso files, you should run rsrc with -arch=amd64, which you don't mention - why? If you run without -arch=amd64, then I would expect you to get compilation errors from Go compiler when linking with .syso - but you don't mention errors either, which again confuses me. Finally, AFAIU, ia64 is something very different than amd64, so again I'm super confused why do you seem to be trying to mix both? Do I miss something?

@fcharlie
Copy link

You can also use bali

@ghost
Copy link
Author

ghost commented Apr 17, 2020

Other than that, I'm confused as to what processor architecture you're using. You mention amd64 version of Go - does it show up as so when you run go env GOARCH? If yes, for .syso files, you should run rsrc with -arch=amd64, which you don't mention - why? If you run without -arch=amd64, then I would expect you to get compilation errors from Go compiler when linking with .syso - but you don't mention errors either, which again confuses me.

go env GOARCH shows amd64
I ran rsrc without -arch=amd64 and no compilation errors were reported.
If I run it with -arch=amd64 option, nothing changes.

Ok, I will use either goversioninfo or bali.

@ghost ghost closed this as completed Apr 17, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants