Request: --ico should not really require a rebuild
See original GitHub issueCurrently it’s quite inconvenient and confusing (not clear) that --ico
option requires --build
.
It is possible (and easy enough) to change the icon and other resources of an executable, for example by using https://github.com/electron/rcedit
However, applying this tool on the final nexe app (after the script is embedded) will break the executable:
I assume it can be safely applied to a pre-built executable
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Rebuild Icon Cache in Windows 11 Tutorial
5 Follow the instructions in the command prompt to rebuild the icon cache. If you do not restart the PC now, you will...
Read more >Visual Studio will not show my .ico for project icon
This process should be so simple and easy to implement, just changing the solution's icon to an acceptable-format icon.
Read more >Setup project and data file problems redux - MSDN - Microsoft
We only need to rebuild the project and the Visual Studio Setup project, with the application project's primary output in it. Then you...
Read more >Has the ICO really given up? - Farrer & Co
The ICO acknowledged that diverted resources and new priorities would see changed approaches and understandable delays in dealing with subject ...
Read more >Information Commissioner calls for an end to the excessive ...
“Change is required to rebuild trust that will enable more victims to seek the justice to which they're entitled.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@simonbuchan de42dd94adf9b1fe6bdf438359965a532540a5f8 re-orders the download step and its now performed before the plugins/patches run. So patches can operate on the file.
With further testing, the above doesn’t quite work for this in general: the problem is that
patches
andplugins
are the last arguments tocompose
innexe.ts
, which means they can’t run any code after thecli
step pulls down the binary.Probably the simplest workaround is to just use the plugin to grab the output path, then run outside the
compile
call: