[Bug 280527] [new port] emulators/ares: open-source multi-system emulator with focus on accuracy and preservation
Date: Sun, 11 Aug 2024 14:43:23 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280527 --- Comment #6 from Stefan Schlosser <bsdcode@disroot.org> --- (In reply to Vladimir Druzenko from comment #4) > emulators/ares depends on devel/librashader, but devel/librashader is rust software - I am not competent enough in the ports framework for rust, so I do not touch such ports. No problem, we just have to wait for another brave committer then :) Well, it's not like ares has a hard dependency on librashader. I could remove my patches which unbunbdle librashader from ares. In this case users would have to build librashader themselfs on their system IF they want to use shaders. There are instructions provided by librashader and on ares github itself. I did the unbundling of librashader because I think it would be a nice experience out of the box for the ares port to have shader support without users needing to do anything in addition. I would actually wait a little longer for a brave committer to commit librashader before we go that way. > Also I see flavor qt5 - can emulators/ares work with qt6 too? Qt5 planned for deprecation in ports, but I don't know exact date. QT6 is currently not supported upstream. I don't know if there are any plans to support QT6 anytime soon. I included the QT5 flavor because of completeness. And because the QT5 flavor is currently broken with LTO, I would actually have no hard feelings removing the QT5 flavor from the port. Maybe just remove QT5 flavor and add QT6 flavor if/when supported by upstream? (In reply to Vladimir Druzenko from comment #5) > There is games/libretro-shaders-slang port (https://github.com/libretro/slang-shaders) - can emulators/ares use it? Of course, that's the sole reason I maintain the games/libretro-shaders-slang port ;) It's behind the SHADER port option: SHADER_RUN_DEPENDS= ${LOCALBASE}/${_SHADERS}/bilinear.slangp:games/libretro-shaders-slang -- You are receiving this mail because: You are the assignee for the bug.