How I create wine app launcher icons on the Mac

Joerg-Cyril.Hoehle at t-systems.com Joerg-Cyril.Hoehle at t-systems.com
Mon Sep 14 12:13:40 CDT 2009


Hi,

On Linux, I have been using .desktop files that freedesktop defines to keep a directory full of icons. They all launch Wine applications.  Often enough, these desktop files are initially create by Wine in ~/.local/share/applications/wine/..., along with the icon files in ~/.local/share/icons/.

Here's how I now have app launcher icons on the Mac:

sips -i ~/.local/share/icons/foo.png --out foo.png
# sips -i converts and *additionaly* adds icon resource to file
# Alas, sips does not understand .xpm
cat sample.command > foo.png
# > overwrites contents but keeps resource fork
mv foo.png ~/Desktop/foo.command
# .command is the finder's suffix for executable shell scripts
chmod a+x foo.command

sample.command contains:
#!/bin/sh
cd /User/me/xyz && WINEDEBUG=-gsm WINEPREFIX=$HOME/.wine exec wine xyz.exe

Afterwards you edit foo.command and change the directory, environment variables and executable names to meet your needs.  Be careful to use an editor that keeps the resource fork.

"Opening" this icon will launch a Terminal where all logs will go. Optionally you may use Cmd-I(nformation) to disable the display of the .command suffix in the finder (unless forced globally). Wine's X11 window opens above the Terminal window.

I wonder whether this functionality could be somehow integrated into the git (winemenubuilder?), or whether developers believe this should be left to "surrounding" projects like Darwine.

What do you think?
	Jörg Höhle
PS: You can wrap up the whole thing into a single shell script using the
cat <<EOF syntax.



More information about the wine-devel mailing list