Daegalus
-
Posts
19 -
Joined
-
Last visited
Posts posted by Daegalus
-
-
17 hours ago, Rafael Brucart said:
I just came from Fedora. I tried manually building in a Debian container, then tried Grunts PKGBUILD in an Arch container, and Daegalus's podman. Nothing worked, so I assumed it was something I was doing. But now I've just switched to native Arch and did Daegalus's pod again. It is working. I can think of only these things:
I believe the installer was running in Fedora only that for whatever reason it occupied 0 pixels on screen. If someone has Fedora they could try the following:
1. Before running the installerrum ElementalWarrior-[version] $HOME/.wineAffinity winecfg2. Go to Graphics setting and enable "Emulate a virtual desktop", put in your monitor resolution
3. Now run the installer command:
rum ElementalWarrior-[version] $HOME/.wineAffinity wine [Path to the installer].exeThe second thing I can think of was case sensitivity for the "WinMetadata" in which case someone could try duplicating it and changing it to lower case.
And the third is perhaps Fedora needs more than "wine" and "winetricks" installed, maybe some other supporting package.
Has anybody got Affinity running on Fedora as of yet?
Also on another note, I am using Affinity Suite 2.1.1 and for me it crashes on creating a New Document. I have to run "winetricks renderer=vulkan" to get it working in virtual desktop which breaks native desktop, for which I revert back with ..."winetricks renderer=gl". However I started again with a fresh prefix and it all worked fine, so not sure what was going on.I have it running on Fedora, and I compiled mine using my container.
I just followed the guide. I got the WinMetadata from a Windows install. Copied it as is directly from the partition.
I'm still using it now. Though, I always run my stuff through Bottles. I can share my bottle config if it makes a difference
-
5 minutes ago, Wanesty said:
i don't believe samba support is that necessary for wine (or is it required to access mounted SMB share ?)
but overall yes i believe i've seen a few warns while configuring the wine32 build.
Its needed for NetBIOS and other networking/sharing stuff in Windows, which Wine has support for. its libsamba specifically, no thte entire samba install. Either way, I wanted to make my wine-builder generic, so even if its not super needed for Affinity, someone else might use it. I just made sure all optional features were enabled that weren't a huge hassle to enable.
-
52 minutes ago, Wanesty said:
oh damn sound like a nightmare
Ya, but its not just Fedora. Ubuntu and Debian do the same thing for Samba as 1 example. My script ontop of the debian docker image requires me to do this package flipping for 2 libraries. I think fedora had it for many more, but its not an isolated issue with just Fedora.
-
1 hour ago, azuredusk10 said:
Thanks for your hard work with this!
Has anyone managed to build wine on Fedora 38? The list of dependencies in the guide contains several packages with incorrect names. When I managed to hunt the correct names down and install them, I could only get the Wine64 build to work and not the Wine32. It kept asking for freetype development headers, which I believe I had installed but it wasn’t recognising.
I tried various other guides for installing dependencies for Fedora but I couldn’t get past that error.
If anyone could share the Fedora build I would greatly appreciate it!
I did this on Fedora 38, and it was a nightmare. For some dependencies you can't have the 64bit and the 32bit at the same time, they overwrite each other. So you have to switch between builds. I even had to do it in Debian in the docker image I made.
I eventually gave up and made the `wine-builder` linked above to get around it. When I get some free time, I might even switch it to using Arch and the PKGBUILD deps like ElementalWarrior suggested, but for now it works fine for building.
-
14 hours ago, ElementalWarrior said:
By defining all those dependencies in docker you're asking for a maintenance pita. You'd be better off using a pacman based root image and having one step just install build deps from the arch aur package
I agree, at the time I was just trying to build it quick, and I don't have much practice using Arch in docker images. It's always alpine, distroless, debian, etc. So I just used what worked for me for quickness.
When I get back from vacation, where I make an arch based one.
-
Just a reminder to those having trouble compiling. I built a Docker image that should let you easily build wine sources from scratch on any distro using Docker containers.
If you are inclined to explore docker or already know it, could be a quicker way to get the sources built.
-
46 minutes ago, SevenStart said:
At such moments I really hope that the moderators or developers of Serif could give some help. I think many underestimate the impact a graphic editing tool like Affinty or Photoshop has on the OS market share.
If a product like Affinity Photo, Designer, etc. worked on Linux, it would attract a lot more people to switch to Linux. Many want to move to Linux but can't because they are extremely dependent on graphics development products. That would also give Serif an enormous boost. Because - albeit small - the Linux market is mostly made up of people who don't feel like Microsoft's or Apple's data monitoring and want to enjoy the many benefits of Linux. They're even willing to pay extra just to stop being dependent on an OS they don't even want to use.
I know from my environment (student from Germany) who would like to switch to Linux but cannot because of such hurdles.
Really that's such a shame. 😞
Agreed, feels like a missed opportunity. I would honestly be willing to pay double the Windows prices for a Linux version.
-
@Wanesty Opened the github bug for it here: https://github.com/bottlesdevs/Bottles/issues/2828, if you wish to provide more context.
-
41 minutes ago, Wanesty said:
oh so it's a binary ? or can you make it build apps like aur can ?
The end result is a package with a fully compiled ElementalWarrior wine build. So everything you get in wine-install as an RPM package that is installed to the system like any other rpm.
The building and sources live in the COPR repo that produce the final RPM.fornothers to install. It's why it's a bit of a hybrid of PPA from Ubuntu and the Arch AUR.
-
1 hour ago, Wanesty said:
please do ! I should have indeed done it, send the issue link if you make one so i could maybe add more details !
if the syntax is similar to AUR PKGBUILDs, i could make a AUR repo and you could just translate it ?
I haven't opened yet, still planning to though. Their ticket template require some debug info from the bottles app and I'm not at my computer
As for copr. It's more a AUR/PPA hybrid. I need to construct a src.rpm, push that up and copr builds a repo and proper RPM that can then be distributed.
-
1 hour ago, Wanesty said:
oooh that's really nice, also you should add a LICENCE to your repo !
Oof my bad, I normally do but forgot. I'll add an ISC license shortly (effectively MIT license)
-
12 minutes ago, Rafael Brucart said:
I am not to sure whether it is helpful to you or anyone but Fedora comes pre-installed with toolbox and podman. So for those who don't want to flood their OS with a million wine dev packages when attempting to build wine, you can create this environment before following Elemantal's guide.
just type:$ toolbox createthen
$ toolbox enterThen install wine dev packages and follow Elemental's build instructions.
---
Alternatively
Wine is far easier to build on Debian/Ubuntu. So Alternatively (and I have no idea if this would work) you can build Wine from a Fedora terminal by enteringDebianenvironment with the following:podman run --rm -it docker.io/library/debianThen install the debian wine dev packages, and then follow Elemental's guide. However I have no idea if the built wine will then work on a Fedora machine so...
The binaries should work, at least mine does. Used podman and my image to build itunder debian, but used it in Fedora.
To be honest, I always forget Toolbox is a thing.
There is also distrobox too.
-
Stayed up way too late getting this working but here is the Docker image. Readme is in the github repo or the package page, take a look to see how to use it. I successfully compiled a ElementalWarrior build with this.
https://github.com/daegalus/wine-builder
https://github.com/daegalus/wine-builder/pkgs/container/wine-builder
podman pull ghcr.io/daegalus/wine-builder
-
30 minutes ago, Grunt said:
Just beware because I don't think winmd files, dotnet or even Affinity binaries are freely distributable files. Recipe (for building) is fine, binaries not so much.
Ya, I am aware. the docker image will just have all the wine deps installed, and a script that runs the wine64, wine32 building, then installs them to wine-install. YOu will mount the Wine sourcecode yourself. This wont run affinity for you. This is just to help people build the ElementalWarrior wine binaries.
-
1 hour ago, SevenStart said:
If you could, you would be my hero. To be honest I'm still having trouble installing all the dependencies to make the applications work.
I had to reinstall Fedora because there were some problems and I didn't know how to uninstall the "make install".Yes, I know I'm a noob, but at least I'm trying.😅
If I find the time and I can figure it out, I will definitely try though. I haven't made a COPR repo before, so might take me a bit.
1 hour ago, Grunt said:And you intend to distribute this docker image?
Yes, as its just a generic builder image. I plan to release it for others to use to create their own consistent builds.
-
5 hours ago, Wanesty said:
a docker image could be nice indeed but i never had docker in my workflow so yea i won't be the one doing it x)
also my install should be relatively clean since it only write :- /bin/rum
- /opt/wines/
- /home/USER/Documents/wine
- /home/USER/Documents/rum
- the wine prefix you made
like, i get what you mean but at least you know where stuff are, and yes i might make a AUR package for rum and maybe an other one for ElementalWarrior's fork if some of you are on Arch (maybe react with a "Haha" if you are and interested)
While that does look clean, installing the 20+ 32bit libraries, and extra 64bit ones that I normally dont need wasn't pleasant. With a docker image, I can have all those dependencies pre-installed inside the docker image, and then just do `docker run wine-builder -v ~/path-to-wine-src:/path-to-wine-in-image` and it will just spit out a working, properly compiled setup, all self-contained.
I'm also a devops engineer, so containers is where i live most of my day, so they are comfortable for me, even though I rarely use them unless necessary on my personal devices. Also I never use RUM or manage my prefixes manually, its why i use flatpak Bottles, so everything lives in one place and a lot of stuff is handled for me. (minus apparently broken dependency installers, I might open a ticket for that with bottles.)
I am also on Fedora (moved from arch a few months ago), so different flow in general from Arch. I might maybe make COPR repo for it (its like AUR for fedora) so it can be used easily on Fedora by others. I'll see what I have time for. -
5 hours ago, Wanesty said:
you can !! but you'd have to use winetricks to install dotnet48 since Bottle own "winetricks replacement" doesn't add the right registry keys.
Good tip, this fixed my bottle for me and now i have all my Affinity stuff in a bottle. Works great there now too. Now I can uninstall Lutris again.
-
I just wanted to provide that I was successfully able to build and run everything. Everything works super well, have all 3 installed now and working.
Now to see if I can get this all working in Bottles. Lutris worked fine.
I will say it was quite annoying to install all the dependencies and getting them to work. Can't wait until this is upstreamed.
Based on how much free time I have, I might look into making a docker image to build this, so it is easier for others to build without polluting their systems. Or I might setup a mirror on Github and use Github Actions to build prebuilt versions. But I got a lot on my plate, so not sure if I will get to any of this. Thanks ElementalWarrior for getting this working.
Affinity Suite v2.0.4 on linux [ Wine ]
in Resources
Posted
I mean ya, that is still a problem. I had to install it the manual way using the external winetricks install. The ticket I opened and you commented in is still open on their github: https://github.com/bottlesdevs/Bottles/issues/2828
Anyways, I have attached my bottles config. Not sure how much it will help, it's fairly default settings.
backup_Affinity.yml