Request for Community help - AO & Awesomonium Now Working In Wine

**DocJones** · Feb 2nd, 2011, 13:36:16

"which wine" returns a link to a wrapper script which hasn't changed for some time. In theory you are right, but macports has some strange techniques to install packages to the system (not to speak of the inability to re-use precompiled object files - everytime i change the patch, the source is re-fetched, extracted, configured, patched and then built and installed)

Anyone knows if i have to recreate the WINEPREFIX each time i rebuild the code?

**Marebone** · Feb 2nd, 2011, 14:26:29

Originally Posted by DocJones

"which wine" returns a link to a wrapper script which hasn't changed for some time. In theory you are right, but macports has some strange techniques to install packages to the system (not to speak of the inability to re-use precompiled object files - everytime i change the patch, the source is re-fetched, extracted, configured, patched and then built and installed)

Oh yeah, it was just a script, didn't remember that.

Were there only one iphlpapi.dll in your system? And was it changed at the time of building?

if the macports stuff gets too weird, you could just do stuff manually:

extract wine sources to some folder,
in Terminal cd to there,
./configure
make -j4 (replace with number of cpu cores)
make install

Then in AO's folder: WINEPREFIX=~/.wine-foo wine Anarchy.exe

You could also get a bit earlier version and build and install it.
Then, in Terminal:

Code:

wine --version

to check if wine's version changes.

Uninstalling wine is also quite easy with command:
make uninstall

Originally Posted by DocJones

Anyone knows if i have to recreate the WINEPREFIX each time i rebuild the code?

Nope, the prefix contains mainly just the registry, and anything you install there with winetricks. Wine's dlls are used from outside of the prefix.

**Marebone** · Feb 2nd, 2011, 14:40:10

Oh, and patching is done before calling ./configure, in the same folder.
patch -p1 < path/to/NotifyAddrChange.patch
patch -p1 < path/to/RawInputDevices.patch

**DocJones** · Feb 2nd, 2011, 14:49:02

Yeah, gonna try this one out after everything fails. Thanks a bunch, will come back.

Oh, and i have 5 patch files to apply

**Lliers** · Feb 2nd, 2011, 15:55:21

You shouldn't need to recreate your WINEPREFIX every time you rebuild wine. If anything in your WINEPREFIX needs updating with the new version if wine, it should do so automatically when you fire up wine. Deleting and rebuilding your .wine directory is only needed if you broke something in your WINEPREFIX (like, you tried to install dotnet20 twice and the second time broke it).

I would recommend that you give up on macports as your means for installing a patched binary because it automates too many things. You have all your dependencies built using macports, so I would recommend the following:

Set the following environment variables:

Code:

setenv CFLAGS "-I/opt/include"
setenv CXXFLAGS "$CFLAGS"
setenv LDFLAGS "-L/opt/lib"
setenv PKG_CONFIG_PATH "/opt/lib/pkgconfig"

If your default shell isn't tcsh but bash, then it would look like this:

Code:

export CFLAGS="-I/opt/include"
export CXXFLAGS="$CFLAGS"
export LDFLAGS="-L/opt/lib"
export PKG_CONFIG_PATH="/opt/lib/pkgconfig"

I don't remember if macports installs X11 in /opt or in /opt/X11, if it does, then you'll need to add "-I/opt/X11/include" and "-L/opt/X11/lib" to the CFLAGS and LDFLAGS respectively. This will help the configure script to find all the dependencies wine needs. You should also make sure that "/opt/bin" (and possibly "/opt/X11/bin") are in your PATH. I think that should be the case automatically if you have installed macports.

Get a copy of the latest wine source code using either "git" or downloading the release tarball, and after extracting the files, "cd" into the source code directory.

Apply your patches, and use the following command:

Code:

./configure --prefix="/path/to/where/you/install/stuff"

Now the above path should be somewhere you'd like to keep wine or somewhere you keep all the stuff you compile manually. For instance, in my case, I use "/usr/local", and I have "/usr/local/bin" at the front of my PATH, so when I run commands, the shell looks for the one I compiled first.

The bottom of the configure output should have some unimportant messages about things it couldn't find such as libv4l, libgphoto2, and libcapi20. Now you're ready to

Code:

make

if everything successfully builds, then

Code:

make install

to put wine into /path/to/where/you/install/stuff/bin

**DocJones** · Feb 2nd, 2011, 23:10:51

Ok, a complete removal of the wine-devel 1.3.12_0 sources and reinstallation came up with the patched iphlpapi_main.c source

And i bypassed the login procedure and got into the game.

AAaaand i could open the in game Store

Great job you all

http://i296.photobucket.com/albums/m...02um230929.png

**Demoder** · Feb 2nd, 2011, 23:16:09

Would it be safe to ask for getting a [solved] tag in the topic of this thread now?

**DocJones** · Feb 2nd, 2011, 23:35:02

... or even perhaps a *gasps* sticky?

i can provide the patch files for 1.3.12, if anyone is interessted...

**Marebone** · Feb 3rd, 2011, 11:39:53

Originally Posted by Demoder

Would it be safe to ask for getting a [solved] tag in the topic of this thread now?

Sounds good, but there is still at least some stuff to do. That is to get those patches to wine's official codebase, so other players don't have to go through same problem solving as DocJones and others had to.
Of course, if we wait long enough, someone, someday, might correct them to Wine. But, I wouldn't hold my breath

I have tried to get the RtlCaptureStackBackTrace corrected to there, but it's turning out to be a bit more complicated than I had thought at first. And it is taking time.

http://www.winehq.org/pipermail/wine...ry/088430.html (+ replies)
http://www.winehq.org/pipermail/wine...ry/088555.html (+ reply)
http://www.winehq.org/pipermail/wine...ry/088576.html

**raw_fox** · Feb 3rd, 2011, 14:24:34

see what they have done to it

Code:

USHORT WINAPI RtlCaptureStackBackTrace( ULONG skip, ULONG count, PVOID *buffer, ULONG *hash )
{
    CONTEXT context;
    ULONG i;
    ULONG *frame;

    RtlCaptureContext( &context );
    if (hash) *hash = 0;
    frame = (ULONG *)context.Ebp;

    while (skip--)
    {
        if (!is_valid_frame( frame )) return 0;
        frame = (ULONG *)*frame;
    }

    for (i = 0; i < count; i++)
    {
        if (!is_valid_frame( frame )) break;
        buffer[i] = (void *)frame[1];
        if (hash) *hash += frame[1];
        frame = (ULONG *)*frame;
    }
    return i;
}

Code:

static inline BOOL is_valid_frame( void *frame )
{
    if ((ULONG_PTR)frame & 3) return FALSE;
    return (frame >= NtCurrentTeb()->Tib.StackLimit &&
            (void **)frame < (void **)NtCurrentTeb()->Tib.StackBase - 1);
}

AO works with 2 patches only, the mouse fix and the adress fix.
The above source was in yesterdays git pull and solved the ingame store crash caused by corrupt frames.

so it may only need to get the 2 needed patches into the wine master ...

**Marebone** · Feb 3rd, 2011, 14:56:05

Oooh, I'll give it a spin when I get back from work!

**DocJones** · Feb 3rd, 2011, 15:56:17

His Awesomesaucyness Kintaii stickified the thread and changed the subject!

**Marebone** · Feb 4th, 2011, 06:24:06

Yay for sticky!

And the fix for RtlCaptureStackBackTrace works for me too, so that is done now.

Then the next one, NotifyAddrChange.
I think this requires first some kind of test cases that pass on Windows.
Then next, try to implement NotifyAddrChange to Wine. Test cases can be used here to test that the implementation actually works just like in Windows.

**DocJones** · Feb 7th, 2011, 21:14:55

Added winetricks/wine DMG files for Mac OS X 10.6 users to OP.

**spookiepants** · Feb 13th, 2011, 23:34:20

thanks all for this thread. I got my OSX machine up and going now, thanks to you all.
too bad FC didn't offer more assistance.

**Lliers** · Feb 14th, 2011, 04:40:00

Easy there. ^.^ Keep in mind that we are unsupported. And Kintaii did reply to one of my whiney complaints which provided the missing tidbit of information that got the mouse-look/steer problem fixed. All in all, back pats all around.

**olterman** · Feb 23rd, 2011, 16:28:54

whats the status on this, is it only playable if you patch yourself or do we have a solution that works for non techies too ?

**DocJones** · Feb 23rd, 2011, 16:30:26

The WINE ticket has been closed. The current version (1.3.14) of WINE contains all patches needed to play the game without much hassling.

**Lliers** · Feb 23rd, 2011, 21:14:41

Not quite. RawDeviceInput patch is still required if you want to mouse look/mouse steer.

**-LL-** · Feb 23rd, 2011, 22:16:46

if I got it right, there is no chance to run AO from a laptop with integrated intel graphic cards, is there? Under XP AO ran kinda acceptable, but here after installing wine with the patches, after the login screen I get a black screen and sometimes WINE crashes. Sometimes Ubuntu crashes directly....

Thread: Request for Community help - AO & Awesomonium Now Working In Wine

Thread Tools

Posting Permissions