61 replies to this topic

[d10sfan]

Hello,

I was wondering if it was possible to make a winebuild with the following patch:

http://bugs2.winehq....nt.cgi?id=15638

It seems that one was made for 1.1.37.

[thedoc]

can you describe the problem in a bit more detail and link me to the WineHQ bugzilla entry?

[doh123]

looks like a very minor patch... shouldn't be hard.  Your not wanting to try it yourself?

[d10sfan]

I would try it myself but I have no idea how. There a tutorial somewhere that I can look at for that?

Thanks for the response.

[DankoB]

doh123 said:

You can also build your own WS2 engines if you need to customize Wine source code or apply patches.

I got this little bit of info from doh in a pm but thought I would share it here. I don't know if I can use it for what I'm working on now, but I ported Clear Sky and Call of Pripyat using wineskin and they both need what d10sfan is referring to. Although I haven't read the entire Wineskin Manual I don't recall seeing anything about custom builds when I perused it. Is this something new doh? Do we need the beta 1.1 to do this? Any info would be great.

Hey doc, here's the link to the bugzilla info....  http://bugs.winehq.o...bug.cgi?id=6971 ......basically when you install the games (CS or CoP) the mouse will only work in one of the two game play situations, the menus, where you select options, trade or converse with the npc's or the regular first person gameplay, it uses the console command exclusive_input_mode 1 (first person gameplay) or exclusive_input_mode 0 (in menu gameplay) It's a pretty easy workaround but I agree with d10sfan, I would probably be playing clear sky a lot more if weren't for the console command drawback.

[DankoB]

I'm all set to give this a try but what do I do with the patch? The instruction at the WineHQ state that you "do it with a command like "patch -p1 < foo.patch" in the wine source directory. You may have to experiment before you get this right. See the manual for patch for details."

It also leads to here which also makes no sense to me.

http://www.gnu.org/software/hello/manual/diff/Merging-with-patch.html#Merging%20with%20patch

Do I save the file as a text file and rename the extension to .patch and place it in the source folder before building?

[thedoc]

the menu-mouse bug has already been fixed in an earlier custom build I made for Red Orchestra.

I suppose this is the same issue.

here's the build: (1.1.34)
http://www.mediafire.com/?lz0otq2m2m0

you need to add this reg entry to the user.reg file to enable the hack:

[Software\\Wine\\DirectInput] 1240428288
"BoxPixels"="10"
"MouseWarpOverride"="force-box"

[d10sfan]

Is that the same bug? From what I remember, UT2004 games had issues with the mouse getting stuck in a box. That really isnt the same thing that is happening here. In Clear sky, there is a bug where you have to use input_exclusive_mode 0 and 1 to use the menus and actually movement (switch between each).

I tried to use your build but STALKER Clear Sky crashes as soon as it loads. The wine log shows this:

err:ntdll:RtlpWaitForCriticalSection section 0xcc3060 "?" wait timed out in thread 001d, blocked by 001a, retrying (60 sec)

The clear sky log shows this:

Loading DLL: xrGameSpy.dll
stack trace:

 
[error][	 126]	: Module not found

[DankoB]

thedoctor45 said:

the menu-mouse bug has already been fixed in an earlier custom build I made for Red Orchestra.

I suppose this is the same issue.

here's the build: (1.1.34)
http://www.mediafire.com/?lz0otq2m2m0

you need to add this reg entry to the user.reg file to enable the hack:

[Software\\Wine\\DirectInput] 1240428288
"BoxPixels"="10"
"MouseWarpOverride"="force-box"

Thanks for the info doc, but regardless wether or not this is the same bug I'd still like to know what to do with the patches....I'm still in the dark with applying them to a custom build.

I just gave it a shot by showing the package contents of the Wine bundle currently in the CS port and swapped out the Wine build...then I rebuilt the prefix and put the registry info back in and started it up but it crashed after the splash screen

[doh123]

DankoB said:

I got this little bit of info from doh in a pm but thought I would share it here. I don't know if I can use it for what I'm working on now, but I ported Clear Sky and Call of Pripyat using wineskin and they both need what d10sfan is referring to. Although I haven't read the entire Wineskin Manual I don't recall seeing anything about custom builds when I perused it. Is this something new doh? Do we need the beta 1.1 to do this? Any info would be great.

yes its new...

viewtopic.php?f=185&t=4467

you get the Wine source how you want it, then use that build thing and it spits out a WineskinEngine.bundle.

the build will work fine with 1.0... though the Xmodmap file in there for keyboard key remapping will not work without Wineskin 1.1 .... I don't have the manual updated for any changes to 1.1, but if you look at the TODO list you can see what changes I have put in the beta.... but I'm not getting much feedback on it.

[d10sfan]

When I try to use the build, I get this:

configure: error: FreeType 32-bit development files not found. Fonts will not be built.
Use the --without-freetype option if you really want this.
An error occured during Wine Configure, build halted.

I have tried using macports to install freetype with the +universal command. I have also tried to install it from source. Neither have worked.

[doh123]

d10sfan said:

When I try to use the build, I get this:

configure: error: FreeType 32-bit development files not found. Fonts will not be built.
Use the --without-freetype option if you really want this.
An error occured during Wine Configure, build halted.

I have tried using macports to install freetype with the +universal command. I have also tried to install it from source. Neither have worked.

what OS are you building on?  the 10.4 freetype devel files are right there in the Wineskin2 folder that it should be accessing during build...  it will only look in the Xcode 10.4 SDK and at the stuff in the Wineskin2 folder... it doesn't build agasint other things installed on your system cuz it has to be portable to all machines.

[d10sfan]

I am using 10.6.3 snow leopard.

[doh123]

d10sfan said:

I am using 10.6.3 snow leopard.

how exactly are you trying to build it?  That shouldn't be an error with my build script.

[d10sfan]

doh123 said:

d10sfan said:

I am using 10.6.3 snow leopard.

how exactly are you trying to build it?  That shouldn't be an error with my build script.

I go into the ws2custombuild directory and type ./build wine-1.1.37

[doh123]

no idea whats gong on then.. freetype is there.

[d10sfan]

Is that directory supposed to be in /var/root/Wineskin/WS2CustomBuild right? That is where the script told me to put it.

[thedoc]

no it's /Users/YOU/Wineskin/WS2CustomBuild :P

[doh123]

/var/root?  this is OSX not Linux...

it goes in your user folder in a folder called Wineskin.. the same folder that Wineskin.app uses for normal wrappers.

[d10sfan]

Ok, I think it was because I was in root. I have moved it to the user/wineskin directory. I still get the freetype error though:

checking for freetype/freetype.h... no
checking for freetype/ftglyph.h... no
checking for freetype/fttypes.h... no
checking for freetype/tttables.h... no
checking for freetype/ftsnames.h... no
checking for freetype/ttnameid.h... yes
checking for freetype/ftoutln.h... no
checking for freetype/ftwinfnt.h... no
checking for freetype/ftmodapi.h... no
checking for freetype/ftlcdfil.h... no
checking for freetype/internal/sfnt.h... no
checking for FT_TrueTypeEngineType... no
checking for FT_Load_Sfnt_Table... no
configure: error: FreeType 32-bit development files not found. Fonts will not be built.
Use the --without-freetype option if you really want this.
An error occured during Wine Configure, build halted.
Cleaning up changes made for the build, if any...
moving build environment back...
Please enter an administrator password if prompted
Please enter an administrator password if prompted

[DankoB]

doh123 said:

you get the Wine source how you want it, then use that build thing and it spits out a WineskinEngine.bundle.

So is there a simpler explanation then what the WineHQ has to say? I'm still unsure from "get the source how you want it" with the patch. How do I save the text from the patches at winehq? as text file? Do I use terminal to apply the patch as well as initiate the build.  Once I understand this process fully I'd be willing to write up a tutorial for you doh  :beer:

[doh123]

patches are just text files... yes

search on google on how to use the patch command... same exact way you'd use it on Linux or anything else. (or you can 'man patch' and read, but finding examples on google is easier)

all the source files are text file as well, it just changes a few lines in the source the patch file indicates to change.

the patch file just changes some of the source code around... then you build it like normal.

[d10sfan]

Hopefully you have better luck with the build script than I did, danko. If it works, could you upload a wrapper (or the wineskin bundle) of it?

[d10sfan]

pepintxa said:

Hello,i´m new in the forum,anyone knows if its possible to play STALKER shadow of chernobil in OS X 10.6.3,i´m just using the ported version,no wine app or boot,or anything,i´m very rookie so if anyone think i´m quite lacy...sorry,i´m not lacy,don´t have been using wine and programs like that and don´t have so much experience cracking...well,the rookie

Anyone know if  STALKER Call of prypyat Is going to be ported?ohhh,that could be soooo cool for noobs without experience running windows on mac

EDIT:Also my english is not good enought to understand some explanations

Those have already been ported on the site. Use the search function and youll see them.

[DankoB]

DankoB said:

I just gave it a shot by showing the package contents of the Wine bundle currently in the CS port and swapped out the Wine build...then I rebuilt the prefix and put the registry info back in and started it up but it crashed after the splash screen

Wow, after re-reading that I feel kind of foolish for not thinking that through....I'm gonna give a go the proper way now.

[DankoB]

OH my god i hate leaning curves, especially when there is no curve. I found a command that was suggested on a Linux forum (after everything else made no sense) that told me to use this to patch and build for CoD4...

http://www.linux-gamers.net/modules/wiwimod/index.php?page=HOWTO+COD4

here's the line I was using.

patch -p1 < dinput.patch

and then it goes through a split second process and comes back and asks me which file to apply the patch to...I thought the patch was applied to the whole source...

this is what I get when i put the patch command in:

dankoB-MacBook-Pro-15:wine-1.1.37 danoB$ patch -p1 < dinput.patch
missing header for unified diff at line 10 of patch
can't find file to patch at input line 10
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|{\rtf1\ansi\ansicpg1252\cocoartf1038\cocoasubrtf290
|{\fonttbl\f0\fmodern\fcharset0 Courier;}
|{\colortbl;\red255\green255\blue255;}
|\margl1440\margr1440\vieww9000\viewh8400\viewkind0
|\deftab720
|\pard\pardeftab720\ql\qnatural
|
|\f0\fs26 \cf0 --- a/dlls/dinput/mouse.c\
|+++ b/dlls/dinput/mouse.c\
--------------------------
File to patch:

[DankoB]

OK, so I tried to apply it to makefile.in and this is what I get....

File to patch: wine-1.1.37/makefile.in
patching file wine-1.1.37/makefile.in
patch unexpectedly ends in middle of line
Hunk #1 FAILED at 330.
1 out of 1 hunk FAILED -- saving rejects to file wine-1.1.37/makefile.in.rej
dankoB-MacBook-Pro-15:WS2CustomBuild

please help?

[doh123]

DankoB said:

OK, so I tried to apply it to makefile.in and this is what I get....

File to patch: wine-1.1.37/makefile.in
patching file wine-1.1.37/makefile.in
patch unexpectedly ends in middle of line
Hunk #1 FAILED at 330.
1 out of 1 hunk FAILED -- saving rejects to file wine-1.1.37/makefile.in.rej
dankoB-MacBook-Pro-15:WS2CustomBuild

please help?

it says the file that was supposed to be patched there was mouse.c

a/dlls/dinput/mouse.c