Daegalus
-
Posts
68 -
Joined
-
Last visited
-
Nice work. My wine-tkg-affinity does the same thing. I just have been busy and never did the second patch or update to 10.4. I can do it later tonight.
-
JFIA reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Which repo/branch is that commit in? I'll pull it out as a patches and add it to my wine-tkg-affinity builds
-
I added the iconw patch posted by ElementalWarrior, I then enabled the built in childwindow patch. That's it. The rest is all build automation. I don't think I tweaked much else. I had a lot more patches for Wine 9.x but with 10, not much is needed.
-
ShadowDrakken reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
I have rebuilt wine-tkg-affinity with 10.3 and the icon patch. It also inlcudes the childwindow fix I have always enabled. Feel free to try it. On the topic ProtonUp or ProtonGear, if my wine-tkg-affinity is stable enough for people, i can ask either of the apps to include the builds i release, they are automated and create Github Releases. [Edit] Oops, I just realized its called ProtonPlus not ProtonGear. I was confusing it with GearLever for AppImages
-
You would need the developer of ProtonUp or Proton Gear to add the repo as a source for builds. But ElementalWarrior doesnt make precompiled builds. So o don't know if we should even be using his name in the repos and projects where we use his patches for builds.
-
I maintain an Affinity TKG at https://github.com/daegalus/wine-tkg-affinity with builds. I only use the patches from @__avg__ as I wasn't sure which of the many commits on the Elemental warrior repo I needed and I could only track down some to their PRs where they were pulled from. But my builds are on Wine10 already. There is an Affinity Linux discord I was in for a while and many in there had success with it, but others didn't. So YMMV.
-
No, but you are acting like an entitled asshole and expecting fast support for an issue that isn't easy to solve and behaves differently on every computer. Wanesty and ElementalWarrior are busy people and have their own lives and priorities. Everything they do is in their free time and for the community, but they are not obligated to you. If you haven't noticed, they haven't messaged at all for a while. Also ElementalWarrior has mentioned that his changes aren't easily upstreamable as they might break many other apps. It might be possible, but it would take time to get it just right. Finally, have you considered using Rum, or Bottles, or any other means of setting it up? Each one has different success rates for people. I get great success using Bottles for my affinity, but not Heroic. Others are the opposite. No one can guarantee it working on Linux for you, especially since Serif does nothing to make it easier for us. This is a long shot in the dark to begin with. So maybe cool your jets. Linux is not perfect and I am not sure why you expect everything to work when trying to use Windows software on Linux.
-
Ignore reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Also, if you copy your `.wineAfinity` to say `.wineAffinity2`, you can experiment with the upgrade and vcrun2022 without breaking your primary installation. Just use the new folder when running the commands. Or just use it as the backup folder Incase you need to revert.
-
Did you make sure to only build within the distrobox? Once its built, you leave the arch distrobox, and go back to the host bazzite. Then do the rum steps from bazzite using the stuff you built under arch.
-
So doing something like that can break your Bazzite installation. Immutable Distros have a different approach to compiling that makes it so you don't break your system or mess with ostree layers. That solution is Distro box. Create an Arch or Fedora distrobox, and do the build in there. The resulting binary can then be moved to the right place on your Bazzite host system once done.
-
Patches from PRs is easy because you can easily download a PR Patch file. The different vkd3d is also not an issue for affinity, but that's separate from Wine. I don't think wine-tkg embeds it. I don't have a patchset for Elemental's stuff because his is just a branch with a bunch of commits ontop of 9.13, but also mixed in with reverts and other stuff. I tried tracking down all the patches he used based on commit messages and find their PRs but not all of them worked right and it was getting messy. I only have _avg_'s patches added. You can find the patches in the custom patches directory in the repo. I have a few others and I enabled childwindow in wine-tkg. If there are missing changes for Affinity that are critical, I'll find patches for them, or make some out of Elemental's commits when I have time. Might just be best to make a separate repo for wine-tkg-on1 and add in what is needed for on1 and do the build.
-
If you guys turn the changes into a patch file, it can easily be dropped in and a build made. We can make a fork for on1 of my repo to keep it clean or we can add it to the affinity one. Either way, once there are patch files, the rest is easy.
-
I think those are pkgbuild related files for Arch. If I understood everything and configured it right, the Arch package should be installable with pacman on Arch
-
You don't, this is a prebuilt release. Just download the package in the releases. You should be able to use it with rum.
-
Just an fyi, I have some prebuilt wines with the patches from _avg_ I haven't tested them thoroughly or recently, but the build and release pipeline now works, so I can quickly add patches and make new builds. These are also build on wine-9.21 and I can keep that updated easily. These builds are based on wine-tkg, so there are some extras and patches already built-in. Let me know how they work or if you have problems. https://github.com/daegalus/wine-tkg-affinity