Description: Mame Executor is a frontend for SDLMame that runs under KDE4. The goal is to provide users with a convenient GUI to configure and launch SDLMame from, instead of having to maintain the rather cumbersome and illogical mame.ini file. It is programmed in 100% OO C++ and aims to be as fast and small as possible while still maintaining a feature rich set of functions and options.Last changelog:
20090612 - V1.01
- A small mistake while we were adding errorchecks ironically added an error in the code, making it randomly impossible to add or remove favorites, we are sorry for this.
20090611 - V1.0
Changes since v0.9-beta: ------------------------- Added translation framework (only a Swedish translation exists, so if you want to help out: get in touch!) Added icon (Thanks Nuno Pinheiro!) Fixed crash in search tab. Games are only launched on double click from the Lists. Fixed build (locating sqlite the proper way from CMake). Included .desktop file. Changed configuration file name according to the KDE specification. General code cleanup/overhaul.
20090118 - Second beta. - Fixed building on debian - changed the name of the configuration file (If you previously installed 0.9b1 rename ~/.kde/share/config/KApp4rc to ~/.kde/share/config/mameexecutorrc to keep your old settings)
Hello,
I really, *really* want to get this working as kxmame is no longer available in the K/Ubuntu package archives, and I feel like I'm pulling teeth when I use the Gnome frontend.
From the build directory, typing make gives this immediate error:
[ 0%] Built target mameexecutor_automoc
make[2]: *** No rule to make target `/usr/lib/libsqlite3.so', needed by `mameexecutor'. Stop.
make[1]: *** [CMakeFiles/mameexecutor.dir/all] Error 2
make: *** [all] Error 2
I have libsqlite3.so installed, except that under Kubuntu 11.04, its actual path is /usr/lib/x86_64-linux-gnu/libsqlite3.so instead of just /usr/lib/libsqlite3.so
Is there any chance that this project is still in active development? What I'd love to see is this project enter the Debian repositories so that anyone can install it easily. But for now, how would you suggest I go about fixing this?
Thank you!
Hi,
we are still developing it but alas we have procrastinated for "a while". A new version is under development with some new features (genre list, and such) and a hefty bit of refactoring.
In this version we are no longer depending on sqlite3 directly but instead using the sql module of Qt itself. So this problem shouldn't appear in the new version. A quick fix in the meantime for your problem might be to create a symbolic link for /usr/lib/libqt3.so..
> A quick fix in the meantime for your problem might be to create a symbolic link for /usr/lib/libqt3.so..
I tried that and it didn't work, nor did making a symbolic link to libsqlite3.so. Make gives the same error.
Hello ;-)
Really, Big Thanks to you!!
It works perfectly, the compilation was very well...
I think it was miss something in the "cmake..." syntax
Excuse me for my english, I'm french ;-)
Hello!!
There is an error message during the make compilation :
m3t4linux@debian:~/Kget/mameexecutor-1.01$ make
[ 3%] Built target mameexecutor_automoc
[ 3%] Building CXX object CMakeFiles/mameexecutor.dir/mameexecutor_automoc.o
In file included from /home/m3t4linux/Kget/mameexecutor-1.01/src/mainview.h:33,
from /home/m3t4linux/Kget/mameexecutor-1.01/src/mainwindow.h:29,
from /home/m3t4linux/Kget/mameexecutor-1.01/moc_mainwindow.cpp:10,
from /home/m3t4linux/Kget/mameexecutor-1.01/mameexecutor_automoc.cpp:7:
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:35:30: error: ../src/imageview.h: Aucun fichier ou dossier de ce type
In file included from /home/m3t4linux/Kget/mameexecutor-1.01/src/mainview.h:33,
from /home/m3t4linux/Kget/mameexecutor-1.01/src/mainwindow.h:29,
from /home/m3t4linux/Kget/mameexecutor-1.01/moc_mainwindow.cpp:10,
from /home/m3t4linux/Kget/mameexecutor-1.01/mameexecutor_automoc.cpp:7:
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:82: error: ISO C++ forbids declaration of ‘ImageView’ with no type
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:82: error: expected ‘;’ before ‘*’ token
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:85: error: ISO C++ forbids declaration of ‘ImageView’ with no type
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:85: error: expected ‘;’ before ‘*’ token
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:88: error: ISO C++ forbids declaration of ‘ImageView’ with no type
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:88: error: expected ‘;’ before ‘*’ token
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h: In member function ‘void Ui_MainView::setupUi(QWidget*)’:
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:291: error: ‘titleImageView’ was not declared in this scope
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:291: error: expected type-specifier before ‘ImageView’
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:291: error: expected `;' before ‘ImageView’
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:301: error: ‘flyerImageView’ was not declared in this scope
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:301: error: expected type-specifier before ‘ImageView’
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:301: error: expected `;' before ‘ImageView’
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:311: error: ‘cabinetImageView’ was not declared in this scope
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:311: error: expected type-specifier before ‘ImageView’
/home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:311: error: expected `;' before ‘ImageView’
make[2]: *** [CMakeFiles/mameexecutor.dir/mameexecutor_automoc.o] Erreur 1
make[1]: *** [CMakeFiles/mameexecutor.dir/all] Erreur 2
make: *** [all] Erreur 2
Can you tell me what I have to do please?
Your soft looks like very good ;-)
G'day,
you should build in a subdirectory rather than in the root. Nevertheless, this is a bug we need to fix, so thanks for pointing it out :)
To fix your problem:
1) download the source tarball
2) extract it
3) enter the directory where it was unpacked (i.e. mameexecutor-1.01/)
4) create a directory called "build" for example (i.e. mameexecutor-1.01/build/)
5) cd build
6) cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ..
(note, the .. is not a typo!)
7) make
8) sudo make install
So the whole crux of the problem was that you attempted to build in mameexecutor-1.01/ rather than in mameexecutor-1.01/build/, I hope I could explain it well enough for you. It's a little strange if you haven't used cmake before.
We really need to get off our arses and write a proper "how to compile" wiki page on our trac soon. If you have any further problems, just ask.
mameexecutor crashes again, when I launch it from terminal, you can see the report here:
http://fpaste.org/paste/17702
please fix it and continue with mameexecutor :)
Hi, in the future please respond on the ticket page on http://trac.mindkiller.com
It's a strange crash, but can you please check the ticket page and try the package i made (and respond back with what it outputs in the shell)?
The first time that I launched the new version from kickoff (KDE menu), mameexecutor crashed, you can see the report here:
http://fpaste.org/paste/16735
Now I can launch mameexecutor, only, from console, running: mameexecutor. If I try, to launch the program from kickoff, simply, it not appears.
how can I launch mameexecutor from kickoff or whitout to use the console?
thanks a lot :)
I saw the answer thanks a lot
but I have no clear something
you say I must install that package (which is on the mameexecutor web page) but must I remove the other package of mameexecutor (which I have installed)?? or must I install the new package without removing the previous?
I did not write this comment on the mameexecutor web page becouse I can't login...
sorry for my english... you know why xD
For those feeling adventurous you can check out SVN trunk to see the feature in action. However I'm unsure how you users want this to work. Should it search for *name* or name* or do you want a fully fledged search like "+foo +bar -baz"? At the moment it just searches for *name* as that seemed the most logical choice.
Also note that the layout for the search tab is only experimental, it will be polished later.
Glad to hear that! I'd personally prefer name*, since users mostly write the beginning of a name they search for, but I don't really care, *name* is also not a bad choice ;) (And it would be even better is a user would be able to choose whether he/she wants name*, *name*, or full search with wildcards like ?)
Second thing. When one chooses directories where hers/his roms are stored, the directories are listed in the text field below (see my screenshot), and that's why I think the text field on the right side (the one marked in red) is unneeded, since it never stores any information (the folder paths are shown below)
http://img195.imageshack.us/i/mameexecutor.png/
Thanks for your input. Yes, I think a search where you can specify wildcards yourself would be better. Gives more freedom/control to the user.
About the file dialog you are right. I didn't even think about the fact that it was not used. Will look into changing that.
But it would be IMO better for a user to specify, what kind of search he/she wants. Somebody might be thinking, why he e.g. can't find "Metal Slug" when he writes "meta" and not many people know wildcards good enough to guess that one would have to write "meta*"
One more thing. I started translating, and there are description for e.g. the usage of certain folders and what do they do (e.g. "nvram" folder, "memcard" folder). I cannot find a way to reach that description inside the program.
There are no "What's this?" entries in the main menu, and "What's this?" cannot be used when folder selection window comes up. How can one obtain any descriptions/help inside the program?
Second thing - in the main menu there's "Help" dropdown menu, with "Mame Executor Handbook", but clicking it gives me:
"Plik lub katalog help:/mameexecutor/index.html nie istnieje"
which means:
"File or folder help:/mameexecutor/index.html does not exist"
Is it my system's bug or haven't you yet made any documentation?
No there isn't any docbook for ME yet :/ And also there is probably a lot to be done about what's this/tooltips. In the general spirit of coders we have neglected that side.
I think it would be better if we discussed this on the forum, so other people here aren't spammed by our "boring" conversations ;) I will look into the docbook/translation stuff as soon as i get some time free.
Ratings & Comments
53 Comments
I REALLY want to use this program! There is no MAME frontend for KDE other than this. If it is orphaned, can it at least be offered a new maintainer?
Please, please, please.
Hello, I really, *really* want to get this working as kxmame is no longer available in the K/Ubuntu package archives, and I feel like I'm pulling teeth when I use the Gnome frontend. From the build directory, typing make gives this immediate error: [ 0%] Built target mameexecutor_automoc make[2]: *** No rule to make target `/usr/lib/libsqlite3.so', needed by `mameexecutor'. Stop. make[1]: *** [CMakeFiles/mameexecutor.dir/all] Error 2 make: *** [all] Error 2 I have libsqlite3.so installed, except that under Kubuntu 11.04, its actual path is /usr/lib/x86_64-linux-gnu/libsqlite3.so instead of just /usr/lib/libsqlite3.so Is there any chance that this project is still in active development? What I'd love to see is this project enter the Debian repositories so that anyone can install it easily. But for now, how would you suggest I go about fixing this? Thank you!
Hi, we are still developing it but alas we have procrastinated for "a while". A new version is under development with some new features (genre list, and such) and a hefty bit of refactoring. In this version we are no longer depending on sqlite3 directly but instead using the sql module of Qt itself. So this problem shouldn't appear in the new version. A quick fix in the meantime for your problem might be to create a symbolic link for /usr/lib/libqt3.so..
That's *great* to hear that you're working on it! Can't wait to see it when it's ready. I'll try linking and see if that works...
> A quick fix in the meantime for your problem might be to create a symbolic link for /usr/lib/libqt3.so.. I tried that and it didn't work, nor did making a symbolic link to libsqlite3.so. Make gives the same error.
Hi, Mame Executor looks great yet I couldn't try it out because of a sdlmame dependency to gconf. Can I use Mame Executor with xmame-sdl? Regards,
You can try ;) I think you just need to select the xmame executable and see if it will work.
Hello ;-) Really, Big Thanks to you!! It works perfectly, the compilation was very well... I think it was miss something in the "cmake..." syntax Excuse me for my english, I'm french ;-)
Hello!! There is an error message during the make compilation : m3t4linux@debian:~/Kget/mameexecutor-1.01$ make [ 3%] Built target mameexecutor_automoc [ 3%] Building CXX object CMakeFiles/mameexecutor.dir/mameexecutor_automoc.o In file included from /home/m3t4linux/Kget/mameexecutor-1.01/src/mainview.h:33, from /home/m3t4linux/Kget/mameexecutor-1.01/src/mainwindow.h:29, from /home/m3t4linux/Kget/mameexecutor-1.01/moc_mainwindow.cpp:10, from /home/m3t4linux/Kget/mameexecutor-1.01/mameexecutor_automoc.cpp:7: /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:35:30: error: ../src/imageview.h: Aucun fichier ou dossier de ce type In file included from /home/m3t4linux/Kget/mameexecutor-1.01/src/mainview.h:33, from /home/m3t4linux/Kget/mameexecutor-1.01/src/mainwindow.h:29, from /home/m3t4linux/Kget/mameexecutor-1.01/moc_mainwindow.cpp:10, from /home/m3t4linux/Kget/mameexecutor-1.01/mameexecutor_automoc.cpp:7: /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:82: error: ISO C++ forbids declaration of ‘ImageView’ with no type /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:82: error: expected ‘;’ before ‘*’ token /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:85: error: ISO C++ forbids declaration of ‘ImageView’ with no type /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:85: error: expected ‘;’ before ‘*’ token /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:88: error: ISO C++ forbids declaration of ‘ImageView’ with no type /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:88: error: expected ‘;’ before ‘*’ token /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h: In member function ‘void Ui_MainView::setupUi(QWidget*)’: /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:291: error: ‘titleImageView’ was not declared in this scope /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:291: error: expected type-specifier before ‘ImageView’ /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:291: error: expected `;' before ‘ImageView’ /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:301: error: ‘flyerImageView’ was not declared in this scope /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:301: error: expected type-specifier before ‘ImageView’ /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:301: error: expected `;' before ‘ImageView’ /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:311: error: ‘cabinetImageView’ was not declared in this scope /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:311: error: expected type-specifier before ‘ImageView’ /home/m3t4linux/Kget/mameexecutor-1.01/ui_mainview.h:311: error: expected `;' before ‘ImageView’ make[2]: *** [CMakeFiles/mameexecutor.dir/mameexecutor_automoc.o] Erreur 1 make[1]: *** [CMakeFiles/mameexecutor.dir/all] Erreur 2 make: *** [all] Erreur 2 Can you tell me what I have to do please? Your soft looks like very good ;-)
G'day, you should build in a subdirectory rather than in the root. Nevertheless, this is a bug we need to fix, so thanks for pointing it out :) To fix your problem: 1) download the source tarball 2) extract it 3) enter the directory where it was unpacked (i.e. mameexecutor-1.01/) 4) create a directory called "build" for example (i.e. mameexecutor-1.01/build/) 5) cd build 6) cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` .. (note, the .. is not a typo!) 7) make 8) sudo make install So the whole crux of the problem was that you attempted to build in mameexecutor-1.01/ rather than in mameexecutor-1.01/build/, I hope I could explain it well enough for you. It's a little strange if you haven't used cmake before. We really need to get off our arses and write a proper "how to compile" wiki page on our trac soon. If you have any further problems, just ask.
sorry but how can I comment on the ticket? I do not see any option that allows me... :P
Sorry, apparently I had misconfigured the bugtracker software. Now you should be able to add comments.
mameexecutor crashes again, when I launch it from terminal, you can see the report here: http://fpaste.org/paste/17702 please fix it and continue with mameexecutor :)
Hi, in the future please respond on the ticket page on http://trac.mindkiller.com It's a strange crash, but can you please check the ticket page and try the package i made (and respond back with what it outputs in the shell)?
The first time that I launched the new version from kickoff (KDE menu), mameexecutor crashed, you can see the report here: http://fpaste.org/paste/16735 Now I can launch mameexecutor, only, from console, running: mameexecutor. If I try, to launch the program from kickoff, simply, it not appears. how can I launch mameexecutor from kickoff or whitout to use the console? thanks a lot :)
I saw the answer thanks a lot but I have no clear something you say I must install that package (which is on the mameexecutor web page) but must I remove the other package of mameexecutor (which I have installed)?? or must I install the new package without removing the previous? I did not write this comment on the mameexecutor web page becouse I can't login... sorry for my english... you know why xD
No, you don't have to. Just download the new source code and install it as you did with the previous version.
I reported a issue: http://trac.mindkiller.com/ticket/7 thanks :D
See answer at ticket page for details.
For those feeling adventurous you can check out SVN trunk to see the feature in action. However I'm unsure how you users want this to work. Should it search for *name* or name* or do you want a fully fledged search like "+foo +bar -baz"? At the moment it just searches for *name* as that seemed the most logical choice. Also note that the layout for the search tab is only experimental, it will be polished later.
Glad to hear that! I'd personally prefer name*, since users mostly write the beginning of a name they search for, but I don't really care, *name* is also not a bad choice ;) (And it would be even better is a user would be able to choose whether he/she wants name*, *name*, or full search with wildcards like ?) Second thing. When one chooses directories where hers/his roms are stored, the directories are listed in the text field below (see my screenshot), and that's why I think the text field on the right side (the one marked in red) is unneeded, since it never stores any information (the folder paths are shown below) http://img195.imageshack.us/i/mameexecutor.png/
Thanks for your input. Yes, I think a search where you can specify wildcards yourself would be better. Gives more freedom/control to the user. About the file dialog you are right. I didn't even think about the fact that it was not used. Will look into changing that.
But it would be IMO better for a user to specify, what kind of search he/she wants. Somebody might be thinking, why he e.g. can't find "Metal Slug" when he writes "meta" and not many people know wildcards good enough to guess that one would have to write "meta*" One more thing. I started translating, and there are description for e.g. the usage of certain folders and what do they do (e.g. "nvram" folder, "memcard" folder). I cannot find a way to reach that description inside the program. There are no "What's this?" entries in the main menu, and "What's this?" cannot be used when folder selection window comes up. How can one obtain any descriptions/help inside the program? Second thing - in the main menu there's "Help" dropdown menu, with "Mame Executor Handbook", but clicking it gives me: "Plik lub katalog help:/mameexecutor/index.html nie istnieje" which means: "File or folder help:/mameexecutor/index.html does not exist" Is it my system's bug or haven't you yet made any documentation?
No there isn't any docbook for ME yet :/ And also there is probably a lot to be done about what's this/tooltips. In the general spirit of coders we have neglected that side. I think it would be better if we discussed this on the forum, so other people here aren't spammed by our "boring" conversations ;) I will look into the docbook/translation stuff as soon as i get some time free.