Jump to content

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

Slice

Member Since 07 Jul 2011
Offline Last Active Mar 29 2019 12:40 PM
*****

#108110 kill all wineskin processes

Posted Gcenx on 21 February 2019 - 04:23 PM

View PostSlice, on 21 February 2019 - 03:28 AM, said:

In the current Wineskin version there should be added
"killall wine-prebooter"

Also already fixed in the current Unofficial, it no longer killers the processes instead I use “wineserver -k” that’s also kills the running processes not just the main process. (In most cases)


#107367 Unofficial Wineskin Project

Posted VitorMM on 08 April 2018 - 03:42 PM

View PostGcenx, on 02 April 2018 - 04:01 PM, said:

  • This includes the GPU detection fix by "Markus Stoll" merge request on sourceforge.

Been working on an update to make that specific part even better, with deep video card detection, more accurate and with a much wider support than the one that was been used by WineskinLauncher :)

I've reported that a long time ago, but still didn't had the chance to publish the modified Wineskin, although it's ready (however, not tested).

Me and Paul have being talking with doh about releasing a new Wineskin version. We may merge our changes to create a much more stable Wineskin :D

I will upload my modified Wineskin version to Github. In case you want to combine our changes, just submit yours in a pull request or upload your source code somewhere ;)

EDIT: Uploaded my source.
https://github.com/v...251093/wineskin

Just remembering: my source requires my framework, ObjectiveC_Extension, to be build.


#107343 Unofficial Wineskin Project

Posted Gcenx on 02 April 2018 - 04:01 PM

Last Updated -  December 29th/2019
Current version Wineskin-2.9.0.5


DISCLAIMER WINE ON MACOS DOES NOT SUPPORT DIRECTX10/DIRECTX11/DIRECTX12!
I CAN NOT SUPPORT WHAT WINE DOES NOT SUPPORT!!!!!!!




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. (Wineskin-2.9.0.4 no longer tried to launch wineserverkill.exe)
  • 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 "\"
  • Rebuild Wrapper now resets the MAIN EXE to nothing.exe


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 WineCX18.5.0 Steam will download again.
  • Added ffmpeg - removed to avoid Legal Issues
  • Now ntlm_auth is within wstools.bundle/bin
  • Now checks $HOME/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 appName
  • wine64 used over wine within 64Bit wrappers
  • Font Smoothing enabled on wrapper creation
  • Support wine32on64 in both normal and wow64 builds



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
  • Correctly handles wine version string for repacking.
  • Correct GitHub linked used now allows files committed via “git lfs” to download correctly


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.

Spoiler


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

PortingKit
Anyone who uses PortingKit and is running OS X10.8 to 10.14 is now using Unofficial.

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


#103811 Wine STAGING & CSMT Builds - Engines Available

Posted jtnix on 18 June 2015 - 03:16 AM

View PostSlice, on 17 June 2015 - 07:48 AM, said:

At the begin of the discussion I wanted to show you that unmodified WineStage+unmodified Wrapper == not success because WIneStage is developed and supported for linux and developers didn't care about MacOSX specific problems.
See bugs 25486, 29586, 14939, 29598 for DXTn absent support.
It's a pity using my version of libtxc_dxtn with pure WineStage also in not full solution. See what you have
"   libtxc_dxtn (compatibility....)"
this is wrong. It must be a file name  without comments "libtxc_dxtn.dylib", no spaces, no version, no braces.

I don't know how to correct configure.ac to create more correct file name so I did compilation in two steps.
First for configure and creating config.h
Second edit config.h and final build.

Ahh, I see what you mean.  The configure script has quite a funky little sed replace script trying to extract the dylib name from the actual library itself - very strange.  I wrote a simple patch for the configure script so I could keep using the Wineskin Build Engine feature.  Of course this is not the best solution, but here is the patch anyway if someone is interested:
Spoiler

Put that in a file
wine-staging-1.7.44-libtxc_dxtn_configure.patch
in your wine staging src folder (made for 1.7.44 staging release, but will probably work on other recent staging versions) and then run
patch -p1 < wine-staging-1.7.44-libtxc_dxtn_configure.patch

I also noticed that I had to overwrite the libpng.dylib link in the EngineBase Frameworks folder to the new libpng.16.16.dylib I placed in there, or the compile would not link the correct library, despite being explicitly declared in the created config.h !  

I wish I could get my darn linker to create a .dylib for libtxc_dxtn.  I have libtxc_dxtn compiling to an .so no problem, but no matter seemingly where or how I add the -dynamiclib flag to CFLAGS CPPFLAGS or CXXFLAGS, it has no effect, even after
make distclean
.  Slice, I know you mentioned the flag '-dynamic' and I tried that too, but all the online references I've found say to use -dynamiclib.  Either way - I get no .dylib build love. =(

Happy to use yours, though - I just played a few missions in Everquest II and it is the smoothest yet - no libtxc_dxtn or libpng errors in the log file!  Thanks for the WrapperUpdate!!


#103554 MacWine 64bit news!

Posted ovvldc on 08 May 2015 - 07:44 AM

View Postfailury, on 08 May 2015 - 07:38 AM, said:

but we still need the support for direct 10 and direct 11.

Completely different topic.

Also, you want D10 and D11 support, you don't need it in the way you need food, water, shelter and cuddles. Relax ;).


#103506 MacWine 64bit news!

Posted darklord42 on 03 May 2015 - 03:49 AM

thanks to Josh Dubois and Ken Thommas I got wine 64 bit to compile.  Here is the bug report. https://bugs.winehq....ug.cgi?id=38380

But the problem isn't fixed, and the hacks to get it to work are really less then ideal.  So far its only possible with newer versions of gcc, and not clang which forces you to disable the winemac.drv. (only nesscary when compiling wine64).  But again, i did get it to compile and works with my 64bit chess engines.


#103144 Wine STAGING & CSMT Builds - Engines Available

Posted -------- on 22 February 2015 - 02:44 PM

View PostSlice, on 20 February 2015 - 12:56 PM, said:

Thank for the trick
I installed
sudo port install coreutils
and replace readlink -> greadlink so passed the error.

Next stop
$ ./patchinstall.sh DESTDIR="../../wine" --all
usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
	   mktemp [-d] [-q] [-u] -t prefix
ERROR: Unable to create temporary file for patchlist.
What is wrong here?


please also use following switch

--no-patchlist

then it would be fine.


#103119 Building Custom Wine Engine

Posted dankoB on 20 February 2015 - 04:26 PM

Nope, you can use Winery to build your own custom engines...the only thing it doesn't take care of would be patching the source with your preferred patch.

Simply open terminal and cd to the folder the source is in and the use the command patch -p1 >patchname.patch after it is patched open up Winery and click on the plus sign in the main window. It will open up another pane with the option to Build Custom Engine once you've named the engine and pointed winery to the source folder simply click build and it will take care of the rest.