Regarding Updates, Since Wine-Staging Post 2.21 is Basically Done....
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Regarding Updates, Since Wine-Staging Post 2.21 is Basically Done....
Apparently there will be no Official Wine-Staging releases after the current 2.21. The devs haven't the time. There is, however, a fork which is a set of patches that are to be applied to the main development package but I have yet to build a script to deal with the new format.
I have tried the new Wine v3.2 development package and it does not perform as well as 2.21 Staging most notably in 3D rendering affecting diverse apps including CAD but perhaps mostly Gaming. Even if you don't consider yourself "a Gamer" hopefully you realize it is a very important issue that affects the Windows Stronghold, whether that holds any importance to you or not. Personally I see increased migration from Windows both a bane and a benefit and it's difficult to yet see the net effect.
My interest is almost totally subjective since I definitely prefer never having to boot Windows even in a VM. So, has anybody tried building their own wine-staging post 2.21?
There is, however, a fork which is a set of patches that are to be applied to the main development package but I have yet to build a script to deal with the new format.
I thought the Lutris people took over maintaining it. Are you talking about the same thing?
A couple days ago I read this --- Future of Wine-Staging --- which links to a fork and started messing w/ Wine-v3x. That's what prompted this thread. Thanks for the link it seems a new release may actually occur. Hope so as it does make the job of building a package a bit easier and faster. I've been using your wine-staging Slackbuild script, dugan, for many months now (over a year?) and have been hoping I could just edit the url to use it still. Maybe that will come to pass. I hope so.
I successfully used Alien BOB's SlackBuild to build wine-3.2. The only thing I had to do (other than downloading wine-3.2 and wine-staging) was to untar the wine-d3d9 package, change the version number to 3.2, and recreate the tarball. It built without issues, and I am now using it. Just thought I'd throw that out there..
Heads up that I'm not planning to do a lot of WINE gaming myself this month, so testing is appreciated.
Dugan I've been using your package builder for many months and have been very pleased. I am only too happy to give back by installing this tonight and reporting back on hours of gaming application. Kudos and thank you yet again.
# I believe the rule is one more than the number of cores?
((JOBS = $( nproc ) + 1))
There are two problems with this. First the $cores + 1 is just wrong. You can test this yourself by finding a small test program and testing it with -j1, -j2,-j3 and etc. I have found that the gains are reduced as the number of make jobs approaches the number of cores and then becomes slower when you exceed that number. Be sure to turn off ccache if its enabled as it will break the test.
Second, its not good practice to set the make jobs in a build script. Users should configure their preferred number of make jobs with the $MAKEFLAGS environment variable. For example with my 6-core amd cpu I can do this in /etc/profile or any equivalent location. I can then reset it if needed in my interactive environment by exporting a new value.
Code:
export MAKEFLAGS='-j6'
The only time the make jobs should be set in the SlackBuild is if the additional jobs breaks the build or if its an especially heavy compile and more jobs might overheat a system . Examples of these are the pinball game at SBo and libreoffice respectively.
Dugan's build script works just fine and results in a solid wine-staging install of v3x. I spent many hours running various apps and games after installing last night and my results are quite positive.
Fortunately or unfortunately, depending on your POV, I don't have any wet-behind-the-ears apps/games to test with. The latest windows-only game I have is Deus Ex: Human Revolution which is approaching 7 years of age which I run with Steam. Although it does have some quirky behavior if "Use DX11" is enabled that didn't used to work for me at all and now it does. I prefer forcing openGL for both Gamma and stability of graphics but in both cases framerates are very good even with everything maxed out. Additionally when the game first came out is was required to run it "windowed' to avoid some bug that disallowed 360 degree turning/spinning and that is no longer needed. It just works.
Since I have experienced wine "upgrades" that actually reduced performance on older games i still like to play, like World of Warcraft, I was pleased that dugan's v3 install has no such problem. If anything it there is no major change and any changes there might be seem to be toward slightly smoother as compared to 2.21 wine-staging. Even in heavy resource taxing situations like 25-man Raids with a plethora of "adds" I experienced no slowdowns or any kind of sync problems or artifacts and that was with running Discord in a Browser at the same time.
FWIW I'm still having an occasional issue with sound crapping out requiring a relog to recover but that seems to be a pulseaudio/WOW compatibility problem and has nothing to do with Wine. Man! I despise pulseaudio! For years my sound system worked exactly as I told it to. Now this intruder comes along and gets underfoot. Grrrr! Here's hoping apulse only gets better at satisfying whatever the hell apps think it is they need and just let the server do it's freakin job.
That just makes $JOBS an unset variable which can lead to all sorts of problems... Anyways, if you don't want to fix your script I won't stop you...
On my machine, if I run make -j with no argument (without MAKEFLAGS set), I ended up with 20 cc1 programs running concurrently. So, I agree, it can be problematic.
@dugan, if you want to support parallel compilation if users don't have makeflags already set, but still allow them to specify their own, you could put something like the following in place of the ((JOBS=XXXX)) portion. Then you can just have the make command and it will use whatever the user has set or the number of cores + 1.
Code:
MAKEFLAGS=${MAKEFLAGS:--j$(expr $(nproc) + 1)}
Just a suggestion if it's something you're interested in
Hello dugan and thanks for the script update as well as this intriguing reference. I don't like any of the newer expansions of WOW since WOTLK as it seems to me they are substantially dumbed down to entice more and younger players, but old as it is since it must be played on private servers it is important that it be tweaked to be as efficient as possible since so much is server-side and dependent on net speed. The more one can do client-side efficiently the less is required additionally from the server maximizing framerates while minimizing lag while maintaining top-notch graphics for immersion as well as detail.
Currently I have to jump through a few hoops to get that client-side efficiency. One that I dislike having to do for security reasons is
Code:
sysctl vm.mmap_min_addr=4096
but if I don't wine complains when launching WOW. It is apparently a WOW-only issue since that's the only instance in which it complains. So far no problems result but Patrick does warn it is not an ideal situation.
Additionally my command line for WOW is huge LOL, like this
and actually I'd love to figure out how to incorporate 'apulse' into that command but haven't yet been successful.
So regarding these patches which warn that
Quote:
Originally Posted by Readme.md
If ARB_buffer_storage is not present, you're not going to have a good time.
I am reticent to try this until I discover how I make sure that IS present and hopefully without having to add yet an additional long string to the command. It seems I have a long research session in my future.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.