Jump to content
gcenx83

Wineskin Unofficial Update

14 posts in this topic

Recommended Posts

Last Updated - February  25th/2019
Current version Wineskin-2.8.9

 

This project is to be used as a replacement for the official version of Wineskin from doh123 as that has not been updated since 2015.

This project functions on OSX 10.8 to macOS10.14.

Wine versions are downloaded from Winehq and repackeged on your own system into Engines to be used with Wineskin Winery.
 

List of modifications in the Wineskin App (WineskinApp)

  • The Auto-detect GPU feature should never cause malfunction in the port;
  • The Auto-detect GPU feature should have a much bigger accuracy and detect the memory size of integrated video cards as well;
  • The Retina Mode can be enabled from the Screen Options window;
  • Kill Wineskin Processes should kill ALL Wineskin processes.
  • Images (not .icns files) should also be accepted has wrapper icons;
  • LNK files should be able to be selected as a port's run path, so Wineskin can extract the path and flags from it;
  • Winetricks installation can be silent (with no windows) so it's much faster;
  • Disables X11 option if XQuartz is not installed.
  • The first Advanced tab (Configuration) should be much more simple in the first section:
    • The Windows EXE should use Wineskin syntax, including the drive and the flags, (eg. "C:/Program Files/temp.exe" --run) instead of using a macOS reference path (eg. /Program Files/temp.exe) and the flag apart (eg. --run).
  • Advanced Tab "Disabled Gecko installation" checkbox (allows install to be enabled for "Wrapper Refresh" )
  • Able to detect XQuartz installed via macports
  • Integrated fntoggle directly into Wineskin.app, now you can have Standard F keys during wrapper usage.
  • Wine versions not compatible with "mac driver" will have that option disabled.
  • Fixed a long standing bug from official Wineskin "Command Line Wine Test" now works as intended.
  • Ability to map Command as Ctrl (wine 3.17 and above)
  • Ability to map Option as Alt (wine 1.7.4 and above)
  • No longer alters "EXE Flags" meaning if you require a "/" it's no longer changed to a "\"

 

List of modifications for the Master Wrapper (WineskinLauncher)

  • Many fixes when dealing with newest engines.
  • Closes XQuartz on exit if used.
  • Mono is never installed.
  • Able to use XQuartz installed via macports
  • fntoggle will be set on launch and unset on wrapper exit. (If enabled from wineskin.app)
  • gnuTLS included so supported engines can use it, aka using WineCX17.5.1 Steam will download again.
  • Added ffmpeg- removed for the moment
  • Now adds ntlm_auth on Engine change
  • Now checks /opt/Wineskin/lib" for dylib's
  • Added a fixed version of NCurses without this the fixed "Command Line Wine Test" will give terminal errors
  • Gnutls support requires OSX10.9!
  • Bundle ID is now generated from wineserverName instead of wineName
  • Added a missing symlink for the Frameworks version of Gnutls

 

List of modifications in the Winery App

  • Improved - Engine Ordering.
  • Connects to custom WineskinServer.
  • Downloads engines hosted on WineskinServer.
  • Directly download current "Unofficial Master Wrapper Version"
  • "Update" feature will display when new "unofficial Wineskin Winery.app" version is available
  • Wine versions that Require XQuartz to function are hidden by default.
  • Able to read from a local EngineList.txt (in the same folder as Winery.app)
  • Download and repack Engines from winehq
  • Rebuild using Xcode10, now supports “Dark Mode” when using Mojave
  • Correctly downloads engines again on OSX10.8


With a minimum requirement of macOS/OSX 10.8.
With a recommended requirement of macOS/OSX 10.9.


Download;
Unofficial Wineskin Winery.app
Using the above just download then run, directly download the current master wrapper
Don't use keka to unpack as it currently breaks any downloaded applications after unpacking!


About Local EngineList.txt feature;
This feature was added so winery.app can read a local EngineList.txt file, create a text file with that name in the save directory as winery.app this will now override the copy hosted on GitHub , follow the correct Wineskin engine naming style to download Wine to be repacked into Engines.

 

Examples;

 


The above example would download portable-winehq-devel-3.15-osx.tar.gz and repack into WS9Wine3.15


The above example would download portable-winehq-devel-3.15-osx64.tar.gz and repack into WS9Wine64Bit3.15


The above example would download portable-winehq-staging-3.15-osx.tar.gz and repack into WS9WineStaging3.15


The above example would download portable-winehq-staging-3.15-osx64.tar.gz and repack into WS9WineStaging64Bit3.15

This feature was added incase Winehq added a new wine version and I'm not able to update the list on GitHub , so if tomorrow Wine3.16 was released and compiled versions were available for download, its possible to just make a list and add them yourself

 

WS9Wine3.15
 
WS9Wine64Bit3.15
 
WS9WineStaging3.15
 
WS9WineStaging64Bit3.15
 


Please make sure to clear out your users /tmp folder if you have any issues creating wrappers.

Now works with "Porting Kit!!!!!"
Within PortingKit preferences check the box listed “Use unofficial wrapper”
Now PortingKit will use the this master wrapper, meaning it’s possible to use WS10 and 64Bit Engines.

 

 

A Very Special Thanks to;
doh123 - For creating Wineskin
VitorMM - For the modernized code base along with all the included features!
NRG & dankoB - For Testing the initial releases

Edited by gcenx83
Updating was required

Share this post


Link to post
Share on other sites
Advertisement

What is the difference between

Refresh wrapper

Rebuild wrapper

Update wrapper

?

I see no explanation in the interface

I want to note that this Unofficial Wineskin is preferred against official one.

Share this post


Link to post
Share on other sites

Refresh wrapper, launches wineboot sometimes it helps, that usually happens automatically after changing engines.

 

Rebuild wrapper, will remove and remake the wineprefix that’s included within the wrapper.

 

Update wrapper, this option updates the current wrappers files with the master wrappers files. All contents with /Frameworks are replaced with the current Master wrappers version, also replaces Wineskin.app and the WineskinLauncher files. wswine.bundle is preserved along with the contents of /Resources

Share this post


Link to post
Share on other sites

Winery was updated due to a bug with version handling, any engine that contained a “-“ was affected and would need to be downloaded again.

 

This was fixed by Vitor for PortingKit and the same fix used for Winery.

 

 

PortingKit now defaults to use “Unofficial Wineskin Wrapper” for macOS Mojave users.

Share this post


Link to post
Share on other sites
5 hours ago, Tetonne said:

hope this will be dev in 64bit for new os :)

 

Unofficial Wineskin is already 64Bit, with two exceptions;

- WSGamma (doh123 never provides source code)

- Wine*

 

Our biggest issue is CodeWeavers need to release a working solution to run 32Bit code on 64Bit only OS.

 

Wine64 already functions on macOS Catalina, a user already reports making a clean wrapper and wine64 functioning, I’ve already done everything I can currently.

Share this post


Link to post
Share on other sites
15 minutes ago, Slice said:

Can we live without WSGamma?

 

We can, it’s not a hard requirement.

 

Anything that won’t work on 10.15 and above will be disabled.

Share this post


Link to post
Share on other sites

Hi @gcenx83,

Do you have any idea how to make one wrapper for three application?

One wrapper has a size of 1gb while applications are small about 10Mb so there is no reason to create three wrappers.

Is it possibble to create links or small applications that will share same wrapper for these three different applications? And can be started separately.

Share this post


Link to post
Share on other sites
On 6/20/2019 at 8:18 AM, Slice said:

Hi @gcenx83,

Do you have any idea how to make one wrapper for three application?

One wrapper has a size of 1gb while applications are small about 10Mb so there is no reason to create three wrappers.

Is it possibble to create links or small applications that will share same wrapper for these three different applications? And can be started separately.

 

@Slice I don’t really check here too much.

 

You could use CustomEXE launchers for each item installed into the wrapper that works.

 

It’s also possible to shrink the Frameworks contents down if using a Winehq release (those only need libpng15.15.dylib & libfreetype.6.dylib those are inside wstools.bundle anyway), the next wrapper release will support using an external Runtime in $HOME/Wineskin/lib

 

If your interested, I could upload my current Wineskinlauncher to my MEGA to go along with the uploaded Runtime version.

 

Share this post


Link to post
Share on other sites

Hi,

I tried to make new wrapper but replacing Frameworks and drive_c by symbolic links to big wrapper.

Result is 5.6Mb and it works

Снимок экрана 2019-07-04 в 7.10.24.png

But there are some bugs I didn't understand. May be because of different system.reg for the same system.

And strange behavior for launch

Снимок экрана 2019-07-04 в 7.15.24.png

Too many exec***.bat files?

 

 

Share this post


Link to post
Share on other sites
39 minutes ago, gcenx83 said:

 

@Slice I don’t really check here too much.

 

You could use CustomEXE launchers for each item installed into the wrapper that works.

 

It’s also possible to shrink the Frameworks contents down if using a Winehq release (those only need libpng15.15.dylib & libfreetype.6.dylib those are inside wstools.bundle anyway), the next wrapper release will support using an external Runtime in $HOME/Wineskin/lib

 

If your interested, I could upload my current Wineskinlauncher to my MEGA to go along with the uploaded Runtime version.

 

Oh, yes, see you! CustomEXE does the works!

Somehow I didn't see it before.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×