Jump to content

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

Gcenx

Member Since 10 Aug 2014
Offline Last Active Private
*****

Posts I've Made

In Topic: Wineskin Unofficial Update

13 August 2019 - 02:24 AM

View Postvskllee, on 19 July 2019 - 03:18 AM, said:

Does it support macos10.15?

No.

In Topic: WineStagingGnutls3.X+ & WineStagingVulkan64Bit3.X+

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.

In Topic: Catalina and 32bit

23 June 2019 - 04:37 PM

@Zakk if Ubuntu don't change their mind later and the person is a newbie they might as well move to Pop!_OS they said they won't drop 32bit support, so at least a good supported Debian based distro will still have 32Bit support.

And I agree I don't see a decent macOS solution appearing for a good while at this rate, it's sad considering CodeWeavers were making the most money from macOS ports. I only see it happening faster if Value wants to add official Proton support on macOS


@ovvldc QEMU might be slow and I wouldn't even mind if it covers running DirectX9 and below games at playable rates, Hangover on the other hand I can't even launch the few games/programs I had tested. On Reddit someone responded to me saying they did run a few programs on an arm64 version of Ubuntu but on straight Linux it wouldn't even run those same programs.

In Topic: Catalina and 32bit

22 June 2019 - 02:59 PM

The Linux situation is vastly different then on macOS 32Bit libs being removed is different then outright blocking 32Bit code execution like macOS.

CodeWeavers are working on different avenues but it’s not like we will get any confirmation until they are ready (None Discloser Agrements) , this won’t reflect Winehq.

I personally have been contributing directly to https://github.com/P...nicis-winebuild , qparis added a Hangover environment and builder but hangover is basically useless.

It also already integrated the custom version of clang from ccdavis for all macOS builders but -mwine32 that it provides is not usable at precent for wine, lightly needing patches that we frankly might never see until CodeWeavers are ready to release them.

In Topic: Wineskin Unofficial Update

06 June 2019 - 01:08 AM

View PostRastaFabi, on 05 June 2019 - 08:16 PM, said:

Hi @Gcenx, I just wanted to report, that your wineskin fork apparently is working fine on macOS Catalina.
While I did not test existing wrappers I created a new one with a 64bit engine (4.7). Wineskin proceeded to create the wrapper and I did launch wineconfig.exe, regedit.exe and some more tools. Checking the wine environment I found the expected: syswow64 (the 32bit directory :huh:) is empty, as the 32bit wine process setting it up just did not run.

Yeah since on prefix creation wine couldn't function so
wine wineboot
would have failed but
wine64 wineboot
would have functioned.

I recently make sure to have Wineskin default to using wine64 over wine when available, I had the same results when testing on Mojave with 32bit mode disabled.
Still I'm a little surprised it even worked at all considering all the engines other then then the CX ones are from winehq.


If you replace the wswine.bundle contents with a pure 64Bit compile and rebuild the wrapper (ignoring the error about wine) it will function.
When I have some time I might do a proper set of updates more aimed at Catalina

If you would like a pure64 compile to play with let me know I can thrown one together.

Edit;
I should explain a little more, even if you compile wine as only 64Bit you will get the exact same results as you experienced here, the syswow64 directory and other 32bit folder will still get created by using “wine64 wineboot”