Jump to content

Binary releases and tests


Slice
 Share

50 posts in this topic

Recommended Posts

2 hours ago, Slice said:

It should not be opened.

The file used as is in Wineskin which has own routines to unpack.

I tested. Download the file from my post and unpack it. No issue!

Ah OK, accessible through 7zip Archiver (Wine). Thanks.

Screenshot 21.png

 

#EDIT: ..and definitely, it doesn't need to be decompressed

Edited by Badruzeus
Link to comment
Share on other sites

tanks a lot for this new release :)

drag and drop here : ~/Library/Application\ Support/Wineskin/Engines

try to build a new wrapper with Wineskin Winery.app

while it's ok with :

MyCoolWrapper_WS9Wine2.22

- MyCoolWrapper_WS9WineSherry-2.11-2

can make it work with WS9WineSherry-4.0.tar.7z (it's detected obviously)

any idea?

regards

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

I took release wine-4.1, apply patches of Staging-4.1, and some of my paches hackintosh-specific.

It is WineSherry 4.1, 32bits and 64 bits.

They tested and works in some cases better the older engines. Anyway older engine sometimes can be better. Keep several versions!

 

WS9WineSherry-4.1-3.tar.7z

WS9WineSherry64-4.1-4.tar.7z

  • Like 3
Link to comment
Share on other sites

There is my latest 64bit engine. Vulkan support included but it is on very initial state. Wine developers are at the begin of long road.

As well encryption with gnutls3.0 embedded but not full support.

WS9WineXSherry64Bit4.2-14.tar.7z

This engine depends on libraries and the libraries must be exact version. So this is wrapper update obligatiry for this engine

You may have same libraries same version but different compilation. For full success change them to my version

cp -R path-to/WrapperUpdate65/* Game.app/Contents/Frameworks/

WrapperUpdate65.7z

 

  • Like 1
Link to comment
Share on other sites

5 hours ago, Tetonne said:

^thanks a lot slice

question :

 

~/Library/Application\ Support/Wineskin/Wrapper/Wineskin-2.6.2.app/Contents/Frameworks/

or 

~/Library/Application\ Support/Wineskin/Wrapper/Wineskin-2.6.2.app/Wineskin.app/Contents/Frameworks ?

First one.

Correct wineskin for next created wrapper and correct existing wrappers created with old Wineskin.

 

  • Like 1
Link to comment
Share on other sites

I found  big problems with engine depends on a dylib and this dylib depends on /opt/local/lib/xxx.dylib.

So I created new WrapperUpdate7 including more libraries and a script to convert outer dependency to inner one.

This way the wrapper and all its libraries will depend only on libraries provided with the wrapper.

Do the follow

./fix_dependency.sh Game.app/Contents/Frameworks
cp -R path_to/WrapperUpdate7/*  Game.app/Contents/Frameworks/

This way you will get full resolution of dependencies.

WrapperUpdate7.7z

fix_dependencies.sh.zip

  • Like 1
Link to comment
Share on other sites

13 hours ago, IronManJFF said:

Thanks Slice, you are awesome.

Any way to get libgluezilla ?

And what is it?

 

I created engine with experimental Vulkan support. But I have no success

 

Link to comment
Share on other sites

15 hours ago, IronManJFF said:

Wine doesn't want it .. my game wants it. They made a 'launcher' program that requires this library.

 

https://packages.debian.org/search?suite=all&section=all&arch=any&searchon=all&keywords=libgluezilla

 

 

libgluezilla is not in dependencies of Mono. Mono works in WIne.

Link to comment
Share on other sites

On 2/28/2019 at 4:12 PM, IronManJFF said:

Wine doesn't want it .. my game wants it. They made a 'launcher' program that requires this library.

 

https://packages.debian.org/search?suite=all&section=all&arch=any&searchon=all&keywords=libgluezilla

 

 

As Slice also pointed out that nothing todo with wine.

 

You would be better posting what your trying to run in a new thread, just saying you need to have libgluezilla means nothing.

Link to comment
Share on other sites

  • 3 weeks later...
  • 4 years later...

I created new engine able to start 32bit Windows games in Ventura.

WS11WineCXSherry64bit2211-8.tar.7z

And it contains patches to fix the bug with 

 

The engine should be used in Gcenx's Wineskin but the Wineskin Winery doesn't propose my engines. 

To use it you should place my file into

~/Library/Application Support/Wineskin/Engines where other engines locates.

 

A note for developers.

The engine compiled from open-source crossover 22.1.1 using Clang-8 constructed from the same sources. But I applied several patches for wine sources invented inside the Sherry project (wine for hackintosh).

I have two faults. I have no wine64-preloader and have non-working win32u.dll.so. I don't know what is the procedure to produce them so I just copied these files from Gcenx work and pack them into my engine.

If someone wants to follow me then call me. There are many caveats!

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...