KXMame, a port of gxmame to QT/KDE would be a great addition to portage. Along with the port it has other enhancements such as - Customizable toolbar where one can add, remove and change icons of the toolbar buttons. - Customized game icon size (8, 16, 24, 32 pixels or set to 0 pixel to disable game icons.) - Fast. Kxmame is noticably more responsive than gxmame due to various caching.
Created attachment 67238 [details] kxmame ebuild
Created attachment 68723 [details] kxmame-1.1.ebuild Version bump. Added ~amd64 keyword.
OK, this actually belongs to games guys. Reassign.
Hi :) I just wanted to say that the second ebuild (kxmame-1.1.ebuild) worked fine for me on AMD64 :) It would be really great to see it in portage - there aren't many frontends and most of them are not developed anymore... Regards, Maciej Zieba
Version 1.2 was just released. Renaming the ebuild works fine. I would really like to see it in the official portage tree as well.
Renaming to 1.91 works for the v2 'preview' release, which seems to work fine here. I haven't tried v1.2. I'll echo the previous poster's remark - it would be really good to get this into portage. Previously I used gxmame which isn't modular X aware (mind you, neither is xmame, but I've modded the ebuild to install here).
Created attachment 79187 [details] kxmame-2.0_beta ebuild Minor mod for kxmame-2.0_beta, if anyone's interested. Works here. Should really have made this a patch, but there you go.
*** Bug 128725 has been marked as a duplicate of this bug. ***
*** Bug 131258 has been marked as a duplicate of this bug. ***
*** Bug 149741 has been marked as a duplicate of this bug. ***
When I use "kxmame-2.0_beta.ebuild" I get an error while linking, that the XML_... functions cannot be referenced. This error occurs because there is no reference to the expat library. So I added a src_compile section in the ebuild and "patch" the src/Makefile.am file before the real compiling started. Add expat to the libraries that are linked to the executable. src_compile() { sed 's/kxmame_LDADD = $(GLIB_LDFLAGS) $(GLIB_LIBADD) $(LIB_KFILE) $(LIB_KDEPRINT)/kxmame_LDADD = $(GLIB_LDFLAGS) $(GLIB_LIBADD) $(LIB_KFILE) $(LIB_KDEPRINT) -lexpat/g' -i src/Makefile.am kde_src_compile }
Created attachment 149185 [details] kxmame-2.0_beta.ebuild Patch the Makefile.am so expat will be linked to the executable.
I am unable to get kxmame-2.0_beta.ebuild posted on 2008-04-09 to work with sdlmame. I don't think the ebuild references the version that includes the patch for sdlmame. Since xmame is pretty much dead, it would be nice to use the version that has the sdlmame patches.
How is this going? I've seen this program in many distro's repositories, and it seems to work good for almost everyone, so how is it going here in gentoo?
Created attachment 165980 [details] kxmame-2.0_pre20070603.ebuild I changed the ebuild for the last version I found: kxmame-2.0-svn-sdlmame-20070603.tar.bz2 I use the name "kxmame-2.0_pre20070603.ebuild" for the ebuild. It is also placed in my overlay.
Archive of mailing list "kxmame-release" on Sourceforge is empty. Last SVN commit has been made on June 23, 2007. Last CVS commit has been made on May 25, 2007. Last forum activity in middle 2007. Last tarball released also in 2007.
(In reply to comment #16) > Archive of mailing list "kxmame-release" on Sourceforge is empty. Last SVN > commit has been made on June 23, 2007. Last CVS commit has been made on May 25, > 2007. Last forum activity in middle 2007. Last tarball released also in 2007. > It's ok for now, but when this bug was opened it was still being developed.
(In reply to comment #17) > It's ok for now, but when this bug was opened it was still being developed. Sure. But I think there's very low probability of adding dead unsupported project in portage tree now.
yep, seems dead now. reopen if it revives.
