Daegalus
-
Posts
50 -
Joined
-
Last visited
-
Astonish reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
You can still move it if you want. I think the root drive is mount somewhere under /mnt in the distrobox.
-
Just a reminder, you can move the stuff you compile in the distrobox to the main system and not worry about distrobox exports. Since you are building in the same home folder, you can just use rum on the host system instead of in the distrobox. Should simplify the desktop files and running it.
-
Wanesty reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Astonish reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Since it's 32bit errors, my guess is the `mingw32-gcc` it's not on the site but it is on the list I got from TKG. I don't have my editor handy to sort both and do a diff to see what the differences are, but that would be my guess.
-
@Astonish that was probably me, earlier in the thread. You can extract the WinMetadata stuff from the ISO of the windows installer. But that would require a 3-4 gig download. Doing a Flatpak or AppImage is doable, but you would need s script that manages first boot to download the windows iso, extract WinMetadata, then for Flatpak, download Affinity installers, and run them in quiet/unattended mode (distribution related for Flatpak), and then it can all work. For AppImage, we can have affinity preinstalled, or just use the AppImage as a working Wine setup and your Wine prefix is on your machine. There are many variations. We can even use containers directly or through distrobox. In the end it's not hard, just time consuming getting just the right incantation. We can also make Affinity Wine docker images. And people can write a script to make it easier to use and just have something like `affinity-wine install [path to installer]` and it manages the prefix nonsense for you` and then do `affinity-wine run designer` to launch the designer, and make shortcuts to the script. All this is possible, just takes time to set up and build. It's what I was doing on my GitHub. `wine-builder` and `affinity-tkg` can build the patched wine, which already works. And then I can make `affinity-linux` that had all the commands,extras, WinMetadata downloader, etc. I just need to get a couple of hours of free time, which will be soon. To start making all this.
-
Astonish reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Your assumption at the end is correct and can be done. It's technically what Flatpaks, AppImages, and the like kind of do in different ways. It is why they are popular. If you run an Immutable distro, Flatpak and AppImage is one of the only ways to get apps without layering more packages on top of the Immutable base, which is recommended. The issue I see is teaching Distrobox now, and containers, and mounting stuff, etc. Might be easier for some, harder for others. We just need to find a way to automate the WinMetadata step. Either from an ISO, or something. Then we can do all sorts of fancy things. The current problem is distribution/legal, not the technical aspect
-
Astonish reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Astonish reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
You can even do an OpenSuse distrobox and build there. Suse is a bit closer to Fedora in system design and packages so it might be less likely to break between them.
-
@Astonishyou can delete the home folder stuff safely and it should work fine. The system is isolated, so it won't break each other and your main system. Only the home folder is shared in a special way. Also you can run Fedora 40 in distrobox, I think you just need to pass the image flag with fedora-toolbx:40 (look it up though, not sure off the top of my head) This is just a way to get a clean system to compile on and not mess up your main system. Finally, the wine you build under Arch should work on your main system. So you can do the building and compiling on Arch in the distrobox, then the rum steps on your main Fedora. Or in the Fedora distrobox. It's your choice. Since the Home folder is mounted, your main system has access to it. So you can try stuff out. Containers are powerful if you know how to use them or use tools like Distrobox to make it easier. There is I think a GUI someone made for distrobox too. I forget. I havent turned my computer on in weeks with the move. I have been doing everything from my phone.
-
Astonish reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Try So that if it is considered error output it gets caught too. Also, you should look into distrobox. It lets you make sub Distros where you can build and compile stuff, and not affect your main system. So you don't have to reinstall. It will let you create and destroy as many sub Distros for anything, even GUI apps. And you can have other Distros too. So you can run Arch in your Fedora. It uses containers under the hood but adds some magic to make it usable and mounts your drive and home folder inside. Might save you some time. I use it a lot since I use Immutable Fedora.
-
Astonish reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
@Astonish can you share the Yes No list with us. Some stuff is optional
-
Astonish reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Wanesty reacted to a post in a topic:
Affinity Suite V2 on Linux [ Wine ]
-
Looks great to me.
-
Oh, well, I've been a bit distracted, sorry!
-
I just remembered I have working Fedora building on my GitHub builds. Here is a list of the dependencies it uses. Note that some of these might not be needed as they are for the TKG wine build system, so it setups all the tools it uses for automation too. It also uses WoW64, so it only uses the 64bit libraries. If you need the 32 bit libraries, here is the list, but it is highly likely to break:
-
I think we should maybe consider switching our builds to use the WoW64 mode. This lets us compile wine with only 64bit libraries and removes the need for all the i386 libraries. It is what I do on my GitHub builds. Might be worth doing that for simplicity.
-
I run Fedora and Fedora Silverblue, if you give me a day or 2, I can write up which dependencies are needed. My move to Europe is slowing down so I will have some time to start helping out here again.
-
Maybe we can try seeing if Tiny10 or Tiny11 have these files. They are stripped down small ISOs of 10 and 11. Tiny11 core is 2gb and full is 3.7gb