Winemenubuilder
From Wine-Wiki
[edit] introduction
According to the WWN one thing the winemenubuilder does is read out the .lnk files into compatible menu/desktop entries of the corresponding Desktop environment (KDE,GNOME...).
Winehq Bugzilla entry 10277 you can manually run "wine winemenubuilder -r" to uninstall menus whenever you want to (eg. after an app is uninstalled). "wine winemenubuilder -a -r" is even better since it will clean up file type associations too.
[edit] Troubleshooting winemenubuilder
err:menubuilder:extract_icon32 LoadLibraryExW\ (L"C:\\altera\\quartus60\\win\\quartus.exe") failed, error 126
"Error 126" is include/winerror.h:#define ERROR_MOD_NOT_FOUND 126 U. Bonnes speculated: I guess that winemenubuilder is invoked in an too early stage where the executables are not already deployed.
V. Margolen: It first tries to extract icon from file as PE. Then it tries that file as an .ico file. If that fails, it queues itself into RunOnce to be started by wineboot.
But it looks like something really broke that part. We now trying to create links to "c:\"c:\Program Files\Prog\App.exe"". Which wasn't the case before. That's on top of lots of other problems that are still exists in winemenubuilder and still not fixed.
T. Spear: I recall seeing this problem with the deprecated wineshelllink script, although it didn't give this error, as that was not a part of the script. What happens (although not in this case, because of what Vitality explained with the double "C:\") is that under windows, an installer can create a link before the executable, dll, or ico is actually properly extracted. This works because of the way that windows lnk files work. Under wine, since we are actually trying to extract the icon, the executable has to be there, and when it isn't we fall back to running it on the next invocation of wine by the user, by putting it in runonce. As for the "C:\" being doubled, I dunno, but it [definately] wont work at all that way. wine archive
