http://bugs.winehq.org/show_bug.cgi?id=18424
--- Comment #51 from Jonas Maebe jonas.bugzilla@gmail.com 2011-06-19 11:33:23 CDT --- (In reply to comment #50)
I was wondering if I could be of help in diagnosis ...
Just to make it clear: I personally probably won't work further on this (except maybe some things to improve the PS3 controller behaviour). Of course, any diagnostics information you post can be useful to other people interested in working on this.
I have some flight simulators and a joystick I'd like to try out. However, I don't have git, but since this is the only commit I want to try out, can I just download a clean copy of a Wine engine source code and copy-paste your new joystick code into joystick_osx.c?
Yes, you can do that (since the changes do not depend on any other recent wine changes). Rather than copy-pasting, it's however better to copy the patch inside the wine directory, then open a terminal window, change into the wine directory and type patch -p1 < name_you_gave_to_the_patch_file
Note that building wine is not that easy because of all the extra dependencies. I also had to force gcc to generate 32 bit code for the configure process to finish successfully, even though the wiki says that this should no longer be necessary.
In general, I've found the easiest way to build wine is to use http://code.google.com/p/osxwinebuilder/ (it automatically downloads all dependencies and deals with all special parameter requirements), but the downside is that it has no support for applying patches.
Given that wine has a 2 week release cycle for the unstable branch (at least that's what I read somewhere on the wiki), the next unstable release that includes this patch should be out in about 5 days though (and then you should be able to use osxwinebuilding without any special options).