wine users - Apr 2008 - A few questions about trying to fix WINE for running a game correctly

Hi people :)

Eating dinner today I came up with the idea of installing Most Wanted
and try to get it working correctly. It has two issues: Carreer mode
doesn't start after the first FMV, and sound stutters/hangs forever
after 2-3 secs of starting any quick race.

I have some knowledge of C/C++, or at least I think I'm ready to start
"hacking" at WINE's code. However there are some questions I have
in
mind:

1. Should I use WINE git? if so, is there any guide?
2. When I compile WINE's code, must I wait 30 minutes for each
compilation, or will it update only the modified files?
3. Once I've fixed (or at least spotted) the problem, how do I make it
available for others to test and apply it into official WINE?

Thanks in advance :).

Hi people :)

Eating dinner today I came up with the idea of installing Most Wanted
and try to get it working correctly. It has two issues: Carreer mode
doesn't start after the first FMV, and sound stutters/hangs forever
after 2-3 secs of starting any quick race.

I have some knowledge of C/C++, or at least I think I'm ready to start
"hacking" at WINE's code. However there are some questions I have
in
mind:

1. Should I use WINE git? if so, is there any guide?
2. When I compile WINE's code, must I wait 30 minutes for each
compilation, or will it update only the modified files?
3. Once I've fixed (or at least spotted) the problem, how do I make it
available for others to test and apply it into official WINE?

Thanks in advance :).

On Sat, Apr 5, 2008 at 10:25 PM, DARKGuy . <dark.guy.2008 at gmail.com>
wrote:
> Hi people :)
>
>  Eating dinner today I came up with the idea of installing Most Wanted
>  and try to get it working correctly. It has two issues: Carreer mode
>  doesn't start after the first FMV, and sound stutters/hangs forever
>  after 2-3 secs of starting any quick race.
>
>  I have some knowledge of C/C++, or at least I think I'm ready to start
>  "hacking" at WINE's code. However there are some questions I
have in
>  mind:
>
>  1. Should I use WINE git? if so, is there any guide?
>  2. When I compile WINE's code, must I wait 30 minutes for each
>  compilation, or will it update only the modified files?
>  3. Once I've fixed (or at least spotted) the problem, how do I make it
>  available for others to test and apply it into official WINE?
>
>  Thanks in advance :).
>
http://wiki.winehq.org/Developers

-- 
James Hawkins

On Sat, Apr 5, 2008 at 8:25 PM, DARKGuy . <dark.guy.2008 at gmail.com>
wrote:
>  1. Should I use WINE git? if so, is there any guide?
>  2. When I compile WINE's code, must I wait 30 minutes for each
>  compilation, or will it update only the modified files?
>  3. Once I've fixed (or at least spotted) the problem, how do I make it
>  available for others to test and apply it into official WINE?
James' answer was the best, but let me add:

1. Yes, http://wiki.winehq.org/GitWine

2. It updates only the modified files

3. You send a patch to wine-patches

But don't expect it to be easy, and don't forget to write a
conformance test, if possible.