[enhancement] Add Linux build instructions or artifacts

[bootmii]

I'm so happy you could afford that Mac mini MacBook and those $100/year signing keys, but you've neglected other Unix-like platforms, which have a significant market share, especially on Steam. We use Proton to run Balatro, which is great because manually invoking Wine is painful. I don't know if File Roller supports EXEs like 7-Zip File Manager does, for example.

A Linux build should be less work than a macOS build. It would be nice if we had one.

[skyline69]

There will be Linux support when there is a certain level of stability reached

[skyline69]

(I value Linux more than macOS or Windows, that's why I want to reach a certain level of quality first.)

[skyline69]

I'm so happy you could afford that Mac mini and those $100/year signing keys, but you've neglected other Unix-like platforms, which have a significant market share, especially on Steam. We use Proton to run Balatro, which is great because manually invoking Wine is painful. I don't know if File Roller supports EXEs like 7-Zip File Manager does, for example.

Also, what Mac mini?

[bootmii]

Also, what Mac mini?

It is the cheapest model Apple sells, since porting to macOS requires one to use Xcode on a Mac. At least I think it does.

[skyline69]

No haha, I am working on a MacBook

[korewaChino]

Hi, I maintain mods scripts to run Balatro natively on Linux through the native LOVE runtime here.

Managing mods should be very simple as you simply need to add the mod to the Lovely Injector mods folder, loading is done similarly to macOS (and Windows) by pre-loading the injector before running the game.

I can make a PR for basic Linux mod installation by adding an alternative path to the base directory.

[skyline69]

@korewaChino I made a branch and worked on linux support a bit. Could you find ways that the css, which BMM uses is supported on webkitgtk2?

[kasimeka]

@skyline69 i think the issue is missing wayland libs / broken wayland compat, i could reproduce what you're (probably) referring to here, which is running the app but it renders with all layout elements on top of each other. this issue wasn't present when i logged out of my wayland session and into an X11 one.

EDIT: switching back to a wayland session and running the project with GDK_BACKEND=x11 task debug (to force using xwayland) renders properly for me

[kasimeka]

on my machine (KDE 6.3 & today's nixos unstable) when steam is uninstalled xdg-open steam://run/2379780 always opens a window that says "could not read steam://run/2379780." and exits with status code zero. so i opened a PR #127 to your 66-linux-support branch to fix this issue by checking if steam protocol URLs have a handler first with xdg-mime query default then using that method. i've tested it with and without steam and tested that a warning is displayed when firefox is configured to open steam:// instead.

[kasimeka]

with the current config (in my 66-linux-support branch) task release-linux fails at creating the AppImage bundle but I was able to create and run the debian package.

[kasimeka]

after digging around tauri's issues i found another more convenient workaround that allows the app to run natively on wayland. i created a PR that adds it #130 and disables the AppImage target. i can build and run the linux release from this PR, but please note that i'm running this build by unpacking the deb and repackaging it for nixos since i don't use anything debian based.
i see it just works on wayland now, and the layout is correct🤔

[skyline69]

@janw4ld Does the appimage still fail to build? If yes, could you kindly take a look at it?