winepak / winepak-sdk

Platform and SDK runtimes for winepak based applications
50 stars 18 forks source link

32bit broken on redesign branch? #30

Open lionirdeadman opened 6 years ago

lionirdeadman commented 6 years ago

I created a fork (and built it like the README says) : https://github.com/lionirdeadman/winepak-sdk-images/tree/patch-1 to make Gallium-nine changes on the redesign to see if it works.

I tried running : https://github.com/Akusesu/Halo-2/tree/redesign

And well, I tried flatpak run --command=bash net.bungie.H2PC and when trying to run wine, it told me it wasn't a command so I looked to see where it pointed to realise wine: broken symbolic link to /usr/lib/i386-linux-gnu/wine/bin/wine, I'm not sure what I'm doing wrong.

Flatpak list just in case it'd be useful (and yes those come from winepak-local AKA my local repo that I built) :

org.winepak.Platform/i386/3.10-staging                    system,runtime
org.winepak.Platform/x86_64/3.10-staging                  system,runtime
org.winepak.Sdk/x86_64/3.10-staging                       system,runtime

If there's anything I can do to help, tell me.

refi64 commented 6 years ago

To add on to this:

This seems to be a conflict with the way the Compat.i386 extension is extracted and how it's mounted.

When the i386 runtime is built, all the files are moved to /usr/lib/i386-linux-gnu/wine. The files remain here when the Compat extension is created.

Now, when the extension is mounted, it's at /usr/lib/i386-linux-gnu. This ends up meaning that the 32-bit Wine is actually at /usr/lib/i386-linux-gnu/lib/i386-linux-gnu/wine, and all the symlinks in /usr/lib/i386-linux-gnu/bin end up broken.