Wine hacking

Here is a start on my guide to Wine development. I am trying to find out how to do more than just use wine, namely fix some bugs and/or learn how to run things under wine and analyze what they do.

A good first step is to learn how to rebuild (and hack on) wine itself. For a good play by play, take a look at my step by step detail on how to rebuild wine to be able to run TOPO! on my dual core AMD64.

First, let's see what is inside the fedora wine-devel RPM that I hope to depend on:

cd /media/fedora/extras/6/i386
rpm -qlp wine-devel-0.9.35-1.fc6.i386.rpm

/usr/bin/function_grep.pl
/usr/bin/widl
/usr/bin/winebuild
/usr/bin/winecpp
/usr/bin/winedump
/usr/bin/wineg++
/usr/bin/winegcc
/usr/bin/winemaker
/usr/bin/wmc
/usr/bin/wrc

/usr/include/wine/*.h and more

/usr/lib/libwine.so

/usr/lib/wine/*.def

/usr/share/aclocal/wine.m4

/usr/share/man/man1/widl.1.gz
/usr/share/man/man1/winebuild.1.gz
/usr/share/man/man1/winedbg.1.gz
/usr/share/man/man1/winedump.1.gz
/usr/share/man/man1/wineg++.1.gz
/usr/share/man/man1/winegcc.1.gz
/usr/share/man/man1/winemaker.1.gz
/usr/share/man/man1/wmc.1.gz
/usr/share/man/man1/wrc.1.gz

So what is the new stuff in /usr/bin? (they all have man pages)


Have any comments? Questions? Drop me a line!

Adventures in Computing / tom@mmto.org