Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google      Sign In   
  • Create Account

WineStagingGnutls3.X+ & WineStagingVulkan64Bit3.X+


  • Please log in to reply
114 replies to this topic

#61 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 01 May 2019 - 01:29 AM

View Postovvldc, on 30 April 2019 - 09:19 AM, said:

Makes total sense :). No rush!

I made another folder within MEGA
“W3.0.0v-EngineBase - Compile Test”
- WS10WineStagingGnutls4.7
- WS10WineStagingVulkan64Bit4.7

Unlike the official Winehq release these do have FAudio support plus the usual cmd+q patch.

#62 Incredible Hulk

Incredible Hulk

    Professional Member

  • Members
  • PipPipPipPip
  • 185 posts
  • Graphics Card:6750M, OSX 10.12.2
  • Operating System:Other OS/Not specified
  • I like to play:PES, COD, Grid, FNV, RO

Posted 04 May 2019 - 03:26 PM

View PostGcenx, on 01 May 2019 - 01:29 AM, said:

I made another folder within MEGA
“W3.0.0v-EngineBase - Compile Test”
- WS10WineStagingGnutls4.7
- WS10WineStagingVulkan64Bit4.7

Unlike the official Winehq release these do have FAudio support plus the usual cmd+q patch.

Would it be good to add some "Read me" document to Mega for users of "Unofficial Wineskin Winery". Not all are checking this forum and it can be confusing?

#63 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 06 May 2019 - 12:57 AM

View PostIncredible Hulk, on 04 May 2019 - 03:26 PM, said:

Would it be good to add some "Read me" document to Mega for users of "Unofficial Wineskin Winery". Not all are checking this forum and it can be confusing?

I guess I could add a README file but I don't see it getting used just like the first page of "Unofficial Wineskin" thread gets ignored.

If I could be sure the recent Engines worked on macOS 10.8 I would just add them all into a single folder to avoid potential confusion, but I no longer have much free time to test these things full, not like I get feedback anyway :blink:

#64 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 06 May 2019 - 09:44 AM

View PostGcenx, on 06 May 2019 - 12:57 AM, said:

If I could be sure the recent Engines worked on macOS 10.8 I would just add them all into a single folder to avoid potential confusion, but I no longer have much free time to test these things full, not like I get feedback anyway :blink:

Sorry about that.. Hoping to get some free time to test things myself, but it is no happening right now.

#65 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 06 May 2019 - 08:42 PM

View Postovvldc, on 06 May 2019 - 09:44 AM, said:

Sorry about that.. Hoping to get some free time to test things myself, but it is no happening right now.

No need to be sorry, sometimes it just gets disheartening.

#66 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 08 May 2019 - 12:19 PM

View PostGcenx, on 06 May 2019 - 08:42 PM, said:

No need to be sorry, sometimes it just gets disheartening.

:(. The community is unfortunately a bit small. I know that the original Wineskin was used by GOG for their ports. Are the changes that you and VitorMM made being picked up by GOG? I can imagine that the adaptions for newer MacOS would be helpful for them. If so, do they reward you for it, or provide some regular testing feedback?

#67 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 08 May 2019 - 08:26 PM

View Postovvldc, on 08 May 2019 - 12:19 PM, said:

:(. The community is unfortunately a bit small. I know that the original Wineskin was used by GOG for their ports. Are the changes that you and VitorMM made being picked up by GOG? I can imagine that the adaptions for newer MacOS would be helpful for them. If so, do they reward you for it, or provide some regular testing feedback?

Yeah the community here is rather small but the overall amount who use Wineskin is larger then even I expected, now that PortingKit is also officially using it that helps. Some members from here and on Discord are using this to make custom ports within other communities.

GOG haven't picked up the project as far as I know, for the moment I think it best that they don't until we generate a Valid BundleID and wine/-preloader/wine64/-preloader is launched as a sub-process of WineskinLauncher.
I'm not sure if GOG gave any feedback to doh123, of the few games I own that have GOG ports they all used provided Engines nothing custom so who knows.

#68 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 25 May 2019 - 03:14 PM

I’ve been ill yet again recently.

I did build 4.8 already, then refactored my cross-compiler to make use of a patched version of clang-7 that introduces ms_hook_proludge the item that was missing to build truly Winehq compliment Engines.

Also had to make a change to stop Staging patcher reverting FAudio

Updated FAudio to 19.0.5 *
Added mpg123 (mp3 decoding)
* I lightly won’t ever be making FAudio with wma decoding due to it’s licensing.

Edit;
Need to rebuild 4.8/4.9 again due to an upstream wine change that breaks wine64 if mingw isn’t used.

#69 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 27 May 2019 - 01:40 PM

View PostGcenx, on 25 May 2019 - 03:14 PM, said:

Need to rebuild 4.8/4.9 again due to an upstream wine change that breaks wine64 if mingw isn’t used.

That came up on the wine-dev mailing list, IIRC. I fix has been made, so hopefully that is easy to sort out. Happy to test the engines once you do.

#70 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 27 May 2019 - 02:11 PM

View Postovvldc, on 27 May 2019 - 01:40 PM, said:

That came up on the wine-dev mailing list, IIRC. I fix has been made, so hopefully that is easy to sort out. Happy to test the engines once you do.

Did they post a .patch file?


If they really fix the issue then I can use the same patch(s) to rebuild both Wine-Staging-4.8/4.9, while I could upload versions compiled using XCode and mingw I would rather use the cross-compiler due ms_hook_proluge being included.

https://bugs.winehq....ug.cgi?id=47224 That's my bug-report due to the broken 4.8 package because of this change and now updated to include 4.9, I did pass on the information but I know that person is busy.

#71 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 27 May 2019 - 03:28 PM

It sounded like this one: https://bugs.winehq....ug.cgi?id=47238

Fixed with this commit: https://source.wineh...ca15413e36ad775

#72 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 27 May 2019 - 03:56 PM

View Postovvldc, on 27 May 2019 - 03:28 PM, said:

It sounded like this one: https://bugs.winehq....ug.cgi?id=47238

Fixed with this commit: https://source.wineh...ca15413e36ad775

That’s already in Wine-4.9 but the overall issue wasn’t fixed, seems it might be broken for a while upstream.

I’m hoping it can be resolved (by a patch or getting mingw working within Debian stretch) or I might need to do something more drastic.

I’ve been doing pull-requests to Phoenicis-winebuild so I’m hoping qparis is able to figure out the mingw issue since after I added it wine fails to even compile, i’m lightly missing something.

#73 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 27 May 2019 - 04:19 PM

:( sorry to hear that.

#74 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 28 May 2019 - 03:01 AM

View Postovvldc, on 27 May 2019 - 04:19 PM, said:

:( sorry to hear that.

After bashing my head into my desk all day......
I got Cross-Compiling working again from Wine-4.9, Mingw didn't like the wrapper needed for winebuild to inject -m32

Wine-4.8 has an annoying bug forcing X11 driver when build with Mingw.

Edit;
I can properly upload working Wine-Staging-4.9 builds tonight, I might embed the additional libs that or I need to do a wrapper update to add libmpg123/FAudio 19.0.5.
(VKD3D-1.1 is built but mostly useless still)

#75 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 29 May 2019 - 02:41 AM

Uploaded WS10WineStagingVulkan64Bit3.21
Uploaded WS10WineStagingVulkan64Bit4.0
Uploaded WS10WineStagingVulkan64Bit4.1
Uploaded WS10WineStagingVulkan64Bit4.2
Uploaded WS10WineStagingVulkan64Bit4.3
Uploaded WS10WineStagingVulkan64Bit4.4
Uploaded WS10WineStagingVulkan64Bit4.5
Uploaded WS10WineStagingVulkan64Bit4.6
Uploaded WS10WineStagingVulkan64Bit4.7
Uploaded WS10WineStagingVulkan64Bit4.8 *(Wineskin sets "mac,x11 on wrapper creation so bypasses the bug)
Uploaded WS10WineStagingVulkan64Bit4.9
Uploaded WS10WineStagingVulkan64Bit4.10

- Still has FAudio support (Wine-Staging reverts FAudio currently blame Linux)
- It works (Wine-4.8/4.9 needs mingw to compile correctly, but wine-4.8 is kinda broken upstream)
- VKD3D-1.1 support (needs a wrapper update)
- mpg123 - mp3 audio decoding (needs a wrapper update)
- Also support ms_hook_proludge, so things like Steam overlay should function (remove gameoverlayrender from winecfg Libraries tab) aka Winehq like but we have Gnutls and other items Winehq is still missing.


*Wine-4.8, PE files need to be compiled using mingw but due to a bug when mingw is used wine will be forced to using X11 over macDriver. Wine can be compiled without mingw but wine64 does require is due to a broken fallback machanic not working.

#76 RastaFabi

RastaFabi

    Advanced Member

  • Members
  • PipPipPip
  • 59 posts
  • Graphics Card:Intel HD 4000, 1536MB dynamic, shared
    NVIDIA GTX 750Ti, 2048MB, eGPU (Thunderbolt)
  • Operating System:macOS 10.12 (Sierra)

Posted 29 May 2019 - 11:29 PM

Thank you very much for your great and continuous effort, especially since the need to take new hurdles over and over again.
Working great so far, with no obvious regressions whatsoever, though my testing is rather limited. Are there any special areas to keep an eye on, which are not wine, but engine specific?

#77 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 29 May 2019 - 11:46 PM

View PostRastaFabi, on 29 May 2019 - 11:29 PM, said:

Thank you very much for your great and continuous effort, especially since the need to take new hurdles over and over again.
Working great so far, with no obvious regressions whatsoever, though my testing is rather limited. Are there any special areas to keep an eye on, which are not wine, but engine specific?

I can't think of anything Engine specific, usually just the same bugs from Winehq except I build with additional features enabled.


macOS Mojave on the other hand causes hell due to changes with SIP;
  • Permissions needed to control your mouse
  • Permissions needed to go fullscreen (usualy related to mouse)
  • Permissions needed to access Mic
  • Permissions needed to access Web Camera
  • etc
Currently permissions are not passed onto wine processes from Wineskin, that will change but I need time.

#78 RastaFabi

RastaFabi

    Advanced Member

  • Members
  • PipPipPip
  • 59 posts
  • Graphics Card:Intel HD 4000, 1536MB dynamic, shared
    NVIDIA GTX 750Ti, 2048MB, eGPU (Thunderbolt)
  • Operating System:macOS 10.12 (Sierra)

Posted 30 May 2019 - 12:05 AM

View PostGcenx, on 29 May 2019 - 11:46 PM, said:

[…]
macOS Mojave on the other hand causes hell due to changes with SIP;
  • Permissions needed to control your mouse
  • Permissions needed to go fullscreen (usualy related to mouse)
    […]
Currently permissions are not passed onto wine processes from Wineskin, that will change but I need time.

I had some occasional mouse issues with wine 4.7, where sometimes mouse-capturing windows would not regain mouse control after switching applications, but apparently got fixed with 4.9 (if related at all).
No issues with full screen although I do which wine would default to the Mac-native separate space full screen mode. Did not get to much traction when I purposed this on winehq, a few years back…

#79 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 30 May 2019 - 01:11 AM

View PostRastaFabi, on 30 May 2019 - 12:05 AM, said:

I had some occasional mouse issues with wine 4.7, where sometimes mouse-capturing windows would not regain mouse control after switching applications, but apparently got fixed with 4.9 (if related at all).
No issues with full screen although I do which wine would default to the Mac-native separate space full screen mode. Did not get to much traction when I purposed this on winehq, a few years back…

Only Mojave get's the weirder things but not for all games/applications. So that was properly just a winebug just like Wine-4.8 had controller regressions and Wine-4.8 when built with mingw (required!) defaults to X11, Wine-4.9 also needs to be built with mingw for PE files or wine64 is broken.

Yeah I'm annoyed they never did a Virtual Desktop thing with macDriver, maybe they will get it done now that they will be forced too due to the lack of X11 on macOS come 10.15.

#80 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 01 June 2019 - 03:40 AM

Something is really off while I tested WS10WineStagingVulkan64Bit4.9 on my system with the dylibs embedded without any issues.

It gives the same issue as Winehq builds if the dylibs are not embedded, I will try to investigate the problem when I have time but it’s strange everything below 4.8/4.9 don’t need embedded dylibs to function correctly


EDIT;
Resolved seems skipping my usual step of using "install_name_tool" to fix the path within wines .so files now breaks them is my guess.
I've uploaded a working version to MEGA.


EDIT2;
I was informed that the bug affecting Wine-4.8 defaulting to X11 doesn't mean we can't use macDriver it just needs to be changed and since Wineskin already sets
mac,x11
it shouldn't be an issue for us, so I will build it and add to MEGA

#81 palxex

palxex

    Lurker

  • Members
  • 1 posts
  • Graphics Card:NVIDIA Geforce 335M
    Intel HD4000
  • Operating System:macOS 10.12 (Sierra)

Posted 10 August 2019 - 03:45 AM

Thanks for contributing:)
A problem: in recent builds( I've just checked 13 & 12.1 ), many dll.so links to /opt/local/lib, which may not exist on customer's device.
detail for V13:
cabinet.dll.so
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
dbghelp.dll.so
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
l3codeca.acm.so
/opt/local/lib/libmpg123.0.dylib (compatibility version 45.0.0, current version 45.8.0)
mp3dmod.dll.so
/opt/local/lib/libmpg123.0.dylib (compatibility version 45.0.0, current version 45.8.0)
mscms.dll.so
/opt/local/lib/liblcms2.2.dylib (compatibility version 3.0.0, current version 3.8.0)
msxml3.dll.so
/opt/local/lib/libxml2.2.dylib (compatibility version 12.0.0, current version 12.9.0)
opcservices.dll.so
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
openal32.dll.so
/opt/local/lib/libopenal.1.dylib (compatibility version 1.0.0, current version 1.15.1)
winegstreamer.dll.so
/opt/local/lib/libgstvideo-1.0.0.dylib (compatibility version 1405.0.0, current version 1405.0.0)
/opt/local/lib/libgstaudio-1.0.0.dylib (compatibility version 1405.0.0, current version 1405.0.0)
/opt/local/lib/libgstbase-1.0.0.dylib (compatibility version 1405.0.0, current version 1405.0.0)
/opt/local/lib/libgstreamer-1.0.0.dylib (compatibility version 1405.0.0, current version 1405.0.0)
/opt/local/lib/libgobject-2.0.0.dylib (compatibility version 5801.0.0, current version 5801.3.0)
/opt/local/lib/libglib-2.0.0.dylib (compatibility version 5801.0.0, current version 5801.3.0)
/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.5.0)
winex11.drv.so
/opt/local/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0)
/opt/local/lib/libX11.6.dylib (compatibility version 10.0.0, current version 10.0.0)
wininet.dll.so
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)

EDIT: some more:

d3d12.dll.so:
//lib/libvkd3d.1.dylib (compatibility version 3.0.0, current version 3.0.0)
x3daudio1_0.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
x3daudio1_1.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
x3daudio1_2.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
x3daudio1_3.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
x3daudio1_4.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
x3daudio1_5.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
x3daudio1_6.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
x3daudio1_7.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xapofx1_1.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xapofx1_2.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xapofx1_3.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xapofx1_4.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xapofx1_5.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_0.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_1.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_2.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_3.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_4.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_5.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_6.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_7.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_8.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)
xaudio2_9.dll.so:
/root/faudio/build64/libFAudio.0.dylib (compatibility version 0.0.0, current version 0.19.8)

#82 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 11 August 2019 - 02:56 PM

View Postpalxex, on 10 August 2019 - 03:45 AM, said:

Thanks for contributing:)
A problem: in recent builds( I've just checked 13 & 12.1 ), many dll.so links to /opt/local/lib, which may not exist on customer's device.

Here is the commit message I gave for this change within Winebuild;

Quote

Fixing .so files now breaks features when dylibs are not bundled.
Since Wine-4.8 usage of Mingw-w64 cross-compiling the PE files


Basically once wine stated to provide more PE file's patching the paths ended up causing crashes, while patching the correct PE files is a good idea it really makes no difference when the required dylibs are already provided within the master wrapper.
While a later Winehq commit "should" have resolved the issue with PE files getting paths patched it won't resolve this issue if an older wine version needs to be built.

By setting
DYLD_FALLBACK_LIBRARY_PATH
Providing dylibs with correct paths and/or providing all required dylibs it doesn't matter if the path is correct within the .so file or not.
Wineskin already handles setting the required environment variables this is also the case with CrossOver.

TLDR;
That's a none issue when using Wineskin with my provided runtime.

#83 Incredible Hulk

Incredible Hulk

    Professional Member

  • Members
  • PipPipPipPip
  • 185 posts
  • Graphics Card:6750M, OSX 10.12.2
  • Operating System:Other OS/Not specified
  • I like to play:PES, COD, Grid, FNV, RO

Posted 29 August 2019 - 11:08 PM

New set of patches landed from Codeweavers for initializing Metal in winemac driver!?

https://source.wineh...hes/data/169241

#84 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 29 August 2019 - 11:31 PM

View PostIncredible Hulk, on 29 August 2019 - 11:08 PM, said:

New set of patches landed from Codeweavers for initializing Metal in winemac driver!?

https://source.wineh...hes/data/169241

Well yeah it's going to be required considering OpenGL will be getting removed.
We should also start to see additional backend changes that will be needed for future macOS releases.

I'm not sure when the larger changes will will hit but I hope I doesn't take them too long to get everything added in to allow 32Bit process to run within 64Bit threads, but all the other backend changes will need to be inplace before this can happen.

#85 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 30 August 2019 - 07:57 AM

It sounds like still a lot of work to do though. On the upside, it shows that they have a plan at least for 64bit applications.

Whether they will even keep 32bit working on Mac is still an open question. At least we will all want to invest in some more CPU cores is a lot of 32bit-64bit boundaries need to be crossed. Also Apple would have to start selling them, and Intel would have to start making them. Maybe being overtaken by AMD will spur them on, it worked last time when AMD's Athlon 64bit was crushing the Pentiums and Intel developed the original Core architecture...

#86 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 30 August 2019 - 08:00 AM

View Postpalxex, on 10 August 2019 - 03:45 AM, said:

Thanks for contributing:)
A problem: in recent builds( I've just checked 13 & 12.1 ), many dll.so links to /opt/local/lib, which may not exist on customer's device.

Probably specific to the author. Homebrew puts everything in /usr/local. Perhaps symlinking /opt/local to go into /usr/local can solve this? Dirty hack, but small.

#87 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 30 August 2019 - 01:42 PM

View Postovvldc, on 30 August 2019 - 07:57 AM, said:

It sounds like still a lot of work to do though. On the upside, it shows that they have a plan at least for 64bit applications.

Whether they will even keep 32bit working on Mac is still an open question. At least we will all want to invest in some more CPU cores is a lot of 32bit-64bit boundaries need to be crossed. Also Apple would have to start selling them, and Intel would have to start making them. Maybe being overtaken by AMD will spur them on, it worked last time when AMD's Athlon 64bit was crushing the Pentiums and Intel developed the original Core architecture...

CodeWeavers of course want to continue to support macOS since they made the most money via their poring services from macOS customers. See the recent FF port that uses MoltenVK and a version of DXVK to have a working 64Bit client.

32Bit on 64Bit might still take sometime, it would have been nice to have some official statement but that didn’t happen maybe due to the NDA they have with Apple? (I can’t even ask due to said NDA)

Yep with the recent jumps from AMD Intel might get there act together and give us something worth investing into.


View Postovvldc, on 30 August 2019 - 08:00 AM, said:

Probably specific to the author. Homebrew puts everything in /usr/local. Perhaps symlinking /opt/local to go into /usr/local can solve this? Dirty hack, but small.

That’s not required. Since Wineskin already sets
export DYLD_FALLBACK_LIBRARY_PATH=
The built in path only matters if the above isn’t set and the required dylibs aren’t found within wines internal /lib or /lib64 folders then the location built into the .so would be used.

Phoenicis-winebuild project I don’t patch the .so files anymore also (check my commit message for an explanation) and no issues have been reported.
It also bundles all the required dylibs within wine/lib and all symlinks are created within /lib64 like winehq releases. (yeah I’m now also a contributor for Phoenicis due to the work I’ve done on Winebuild)

#88 Gcenx

Gcenx

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 372 posts
  • Graphics Card:Intel Iris
  • Operating System:macOS 10.12 (Sierra)

Posted 02 September 2019 - 03:13 AM

Uploaded WS10WineStagingVulkan64Bit4.15

Upstream wine has added additional requirements again that caused other issues when updating my setup, well it's all working again for now.......


EDIT;
Tried to launch it myself and got the following error
]wine: failed to initialize: dlopen(//lib64/wine/ntdll.dll.so, 258): image not found
The file is indeed where it should be so I'm going to try build it again but this time setting --without-unwind and hoping it works.

#89 ovvldc

ovvldc

    Master Member

  • Members
  • 1253 posts
  • LocationEurope
  • Graphics Card:Intel Iris Plus
  • Operating System:Other OS/Not specified
  • I like to play:stories

Posted 02 September 2019 - 05:54 AM

Thank you.

#90 doepfer

doepfer

    Lurker

  • Members
  • 2 posts
  • Graphics Card:750TI
  • Operating System:OS X 10.11 (El Capitan)

Posted 02 September 2019 - 12:30 PM

Hi,

I wanted to get Vulkan Support to be able to play more graphic intensive games on my Mac.

I am in no way familar with Wine or Wineskin. There have been no clear and intuitive instructions as to how to get this custom build running.

I have no idea what "unofficial wineskin" is referring to, nor where to get it.

Can someone please give me easy and clear instructions how to get this running?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users