Easy way to install OpenRiichi?(Both windows and linux)

WPFilmmaker commented 6 years ago

Hi, first of all thank you for the hard work @FluffyStuff. I would like to ask whether in the future you plan to provide easy to install packages for Windows and the major linux distros (or even better ask to have OpenRiichi added to the official repos). It would increase the userbase and attract players and contributors I think. Not everyone is able to use terminal. I will try on my Ubuntu and report any feedback/issue I have.

FluffyStuff commented 6 years ago

Thanks. You can find an install package and a portable version for windows here. There is also a (mostly) portable version for Debian.

As for having this added to some repos, I've never really thought about that, so I have genuinely no idea what kind of requirements/work are involved in that process. @polarina, what do you think about that? Is that something worth doing? Is it a lot of initial and or maintenance work?

WPFilmmaker commented 6 years ago

@FluffyStuff Thanks for your reply! ~~Does OpenRiichi work under wine? I will try that!~~ (edit: Latest Wine dev runs OpenRiichi like a charm so far, as long as the next verson of wine or OpenRiichi does not breaks something , still an answer to my question to run ubuntu would be still appreciated ;) )

In the meanwhile I followed the steps but I got stuck:

myusername@myusername-pc:~$ git clone https://github.com/FluffyStuff/OpenRiichi.git Cloning into 'OpenRiichi'... remote: Counting objects: 675, done. remote: Compressing objects: 100% (7/7), done. remote: Total 675 (delta 0), reused 1 (delta 0), pack-reused 668 Receiving objects: 100% (675/675), 42.04 MiB | 3.55 MiB/s, done. Resolving deltas: 100% (313/313), done. Checking connectivity... done. stuff@stuff-VirtualBox:~$ git clone https://github.com/FluffyStuff/Engine.git Cloning into 'Engine'... remote: Counting objects: 493, done. remote: Total 493 (delta 0), reused 0 (delta 0), pack-reused 493 Receiving objects: 100% (493/493), 835.18 KiB | 1.37 MiB/s, done. Resolving deltas: 100% (311/311), done. Checking connectivity... done.

myusername@myusername-pc:~$ cd OpenRiichi && make release valac -o bin/OpenRiichi ../Engine/*.vala ../Engine/Audio/*.vala ../Engine/Files/*.vala ../Engine/Helper/*.vala ../Engine/Properties/*.vala ../Engine/Rendering/*.vala ../Engine/Rendering/OpenGLRenderer/*.vala ../Engine/Window/*.vala ../Engine/Window/Controls/*.vala source/*.vala source/Game/*.vala source/Game/Logic/*.vala source/Game/Rendering/*.vala source/Game/Rendering/Menu/*.vala source/GameServer/Bots/*.vala source/GameServer/GameState/*.vala source/GameServer/Server/*.vala source/MainMenu/*.vala source/MainMenu/Lobby/*.vala --thread --target-glib 2.32 --pkg gio-2.0 --pkg glew --pkg gee-0.8 --pkg gl --pkg SDL2_image --pkg sdl2 --pkg stb --pkg pangoft2 --pkg sfml-audio --pkg sfml-system --pkg zlib --pkg win32 -X -lcsfml-audio -X -lcsfml-system -X -Iinclude -X -lm --vapidir=vapi -X -w -X -DGLEW_NO_GLU -D LINUX

stuff@stuff-VirtualBox:~/OpenRiichi$

What should I do now to run OpenRiichi?

About the repo additon please refer to comment 3 of this ticket for a project I give feedback to: https://github.com/bleachbit/bleachbit/issues/305

Each distro has different way but *buntu distros and debian should use the same way and other based on ubuntu (like Mint) have additional packages added by their maintainers. Therefore supporting debian/ubuntu gives a lot of exposure, if other feel to add the software they can become maintainers for their distros.

In case you want to read more (could be out of date though) https://askubuntu.com/questions/75352/how-to-request-a-package-upgrade-in-the-next-ubuntu-release https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages https://www.kubuntuforums.net/showthread.php/54134-FAQ-Requesting-new-packages-new-versions-new-features

Thanks again for the work you put in :)

polarina commented 6 years ago

@FluffyStuff Packaging for the various distributions is something we can consider. It's a fair bit of initial work though, especially if the goal is to make the package available officially in the distributions' repositories (as opposed to just publishing prebuilt .deb/.rpm files).

There's a lot more involved in publishing a package to the official repositories than just making the .deb/.rpm package. You would need to figure out and follow each distributions' rules and best-practices, integrate with their automatic build systems, convincing the developers that the package won't get abandoned the moment they approve it, etc.

Once all that is done though, maintenance should be minimal. I do expect that distributions will from time-to-time rename/move/split-up packages we'd depend on, thus one would need to be willing and ready to spend an hour or two to fix the build scripts each time that happens without much notice.

FluffyStuff commented 6 years ago

This sounds like a lot of work, and I don't think the project is at that stage quite yet (I consider it still very much alpha.) There are a few things in this project that I still need to sink a lot of time into before it would be appropriate to invest time in this. But I will keep this in mind after the next milestone.

FichteFoll commented 5 years ago

I discovered this yesterday and submitted it as a package to the AUR https://aur.archlinux.org/packages/open-riichi-git. Build instructions are clear enough and for installation I resorted to just dumping everything into /opt.

FichteFoll commented 5 years ago

Also, what's the current state of the three branches master, development and next?

FluffyStuff commented 4 years ago

I cleaned up the branches and compilation, so creating packages should be relatively straightforward again (although I plan to delete the makefile and move to cmake instead).

I've decided though that I won't be doing any package maintenance myself. But let me know if there are any issues with creating a package on any distro.

WPFilmmaker commented 4 years ago

@FluffyStuff I would suggest trying pinging the guys at flathub. From what I understood they do the maintaince of their flatpaks (provided there is one maintainer).

This would have 3 beenfit:

1 provide an easy way to install (flatpak) 2 release you from burden of packaging 3 popularize the game as flathub is a popular platform