https://bugs.winehq.org/show_bug.cgi?id=44848
Bug ID: 44848 Summary: Customize CFBundleName in wine_info.plist on Mac? Product: Wine Version: 3.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: loader Assignee: wine-bugs@winehq.org Reporter: pembertona@gmail.com Distribution: ---
Created attachment 60904 --> https://bugs.winehq.org/attachment.cgi?id=60904 Wine menu name on Mac OS X
This is more a question/enhancement than bug, but is it possible to allow the end-user to modify the name of, for example, CFBundleName property in ./loader/wine_info.plist?
When running wine from a .app on the Mac, this would allow customizing the name as it appears in the menu bar. Otherwise all apps appear as simply "Wine" in the menu. (See screenshot).
Is this already possible?
https://bugs.winehq.org/show_bug.cgi?id=44848
Ken Thomases ken@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS|Linux |Mac OS X
--- Comment #1 from Ken Thomases ken@codeweavers.com --- This is not possible in any sort of clean way. CrossOver has a gross hack that achieves this, but it's definitely not suitable for inclusion in Wine.
The issue is that a) the wine_info.plist is compiled into the wineloader and is thus statically determined at build time; and b) the Mac system frameworks don't allow for any dynamism at run time. The bundle name is determined from the executable file or its containing app bundle, not, say, environment variables or user settings.
If you or some wrapper-building app are creating app bundles, you can try to disable inclusion of wine_info.plist into the wineloader and set the app bundle's Info.plist file however you like.
https://bugs.winehq.org/show_bug.cgi?id=44848
--- Comment #2 from Andy P pembertona@gmail.com --- Thanks for the response, Ken!
Regarding disabling inclusion of wine_info.plist, is that something that would have to happen @ configure/make time? ie: require a custom build/package of the wine distro?
https://bugs.winehq.org/show_bug.cgi?id=44848
--- Comment #3 from Ken Thomases ken@codeweavers.com --- (In reply to Andy P from comment #2)
Thanks for the response, Ken!
You're welcome.
Regarding disabling inclusion of wine_info.plist, is that something that would have to happen @ configure/make time? ie: require a custom build/package of the wine distro?
Yes, you'd have to hack on the configure script to remove from WINELOADER_LDFLAGS the linker option which adds in the wine_info.plist file.
https://bugs.winehq.org/show_bug.cgi?id=44848
--- Comment #4 from Andy P pembertona@gmail.com --- @Ken: sounds painful. :)
Well - where there's a will there's a way... one way (an admittedly unclean one, as per your earlier comment) is to edit the binary (I used an app called HexFiend for the Mac). See screenshot. Confirmed this works... however it's manual, error prone, and not so easy to automate.
https://bugs.winehq.org/show_bug.cgi?id=44848
--- Comment #5 from Andy P pembertona@gmail.com --- Created attachment 60911 --> https://bugs.winehq.org/attachment.cgi?id=60911 HexFiend editing
https://bugs.winehq.org/show_bug.cgi?id=44848
Andy P pembertona@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME
--- Comment #6 from Andy P pembertona@gmail.com --- For posterity, here is a bash script that can dynamically rename the CFBundleName property for Wine-Mac users: https://gist.github.com/apemberton/94db4ae8057afc7d1e1037b3b4adea86 - could do this @ run time or in my case as I'm packaging wine in .app, at build time.
https://bugs.winehq.org/show_bug.cgi?id=44848
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Ken Sharp imwellcushtymelike@gmail.com --- Closing bugs marked as worksforme.
-
wine-bugs＠winehq.org