I created a fork due to inactivity

[Herdinger]

Hey guys, I've only stumbled upon this project recently and it rocks.

Sadly it doesn't cater to all my needs and I was eager to contribute back.

After seeing there is huge backlog of Pull Request I decided to Fork and incorporate all the mayor ones.

Of course nobody likes projects which don't have a canonical source of truth so I am more than willing to put to merge all changes back if EmulationStation gets unfrozen, I just want to move the project forward.

Right now I changed the config directory to something sensible on every platform (.config/emulationstation on linux, Appplication Support or .config/emulationstation on OSX and My Documents on Windows) so you have to move your config there if you want to use the fork.

I've also fixed the build on OSX maybe breaking Linux in the process so it would be nice if someone would check that.

The top of the roadmap is reading all issues and pulls for the next few days

https://github.com/Herdinger/EmulationStation

[CWftw]

Thanks for this. I would love to see this project continue to move forward!

[wolf-sigma]

Hey @Herdinger - I've been thinking of doing the same. I'd hate to fork this, but unless @Aloshi can comment on the status of the project, it might make sense. I'm currently running my own fork on a few platforms (MacOS, Windows, and hopefully soon the RPI). I also looked on RetroPie's fork, and they're trying not to deviate too much from upstream.

I'd be happy to collaborate with you on your fork if you want. I have several opinions on how to make this a better project over all. I've currently pulled in a couple PRs and added support for hiding files in my fork.

Send me an email listed on my profile, and we can chat more if you want.

[tynor88]

Good job @Herdinger and @t3hi3x , i will start following your fork. This project has definitely been missing some attention. There are alot of good PR's waiting to be merged in :-)

[eddywebs]

Great work guys, I have recently started to work on the repo as weill, I like to contribute however
While trying to compile emulationstation on a board called orange pi, its fails at 90% using the below error message.
Running an ubuntu arm distribution, and have mali drivers installed.
any ideas why ?

make[2]: *** No rule to make target '/usr/lib/arm-linux-gnueabihf/libGL Sv1_CM.so', needed by 'emulationstation'. Stop. CMakeFiles/Makefile2:301: recipe for target 'es-app/CMakeFiles/emulation station.dir/all' failed make[1]: *** [es-app/CMakeFiles/emulationstation.dir/all] Error 2 Makefile:137: recipe for target 'all' failed make: *** [all] Error 2

[joeelliott]

Could you include a -nosplash option for ES, and maybe allow for a color/alpha option for the main screen white bar in the theme? I dont know if I am able to add a feature request to your repository separately, so I just replied to you here :)

[Herdinger]

@joeelliott I've added a --no-splash option (also the boolean SplashScreen int the settings file) since it was a quick fix. I haven't looked at any GUI code yet but I will look into it.

@eddywebs Sorry I have no idea right now. Basically your Makefile expects a library which isn't there. The weird thing is that CMake detects the library and that's the reason it put it in the Makefile in the first place. It would be helpful if you rebuild from the newest commit with "cmake . > logfile.txt" and post the result

[slikvik55]

Just to check, do we need to compile your fork ourselves?

[wolf-sigma]

@slikvik55 - yeah, at the moment yes. @Herdinger and I are working on some options to download nightly binaries, but the infrastructure isn't setup yet.

[heydonovan]

Any interest in a metadata API strictly for EmulationStation? I'd imagine that it would just return a simple JSON response with release date, publisher, and whatever else people consider important information.

[eddywebs]

Api work is already done by someone > https://github.com/neolao/recalbox-api

It says recalbox but under the hood its all emulationstation, recalbox is
just a buildroot unix with emulationstation.

On Wed, Mar 2, 2016 at 5:52 PM, Donovan Hernandez notifications@github.com
wrote:

Any interest in a metadata API strictly for EmulationStation? I'd imagine
that it would just return a simple JSON response with release date,
publisher, and whatever else people consider important information.

—
Reply to this email directly or view it on GitHub
#563 (comment)
.

Best Wishes;
Adi

[digitalLumberjack]

@eddywebs feel free to read the doc and the source code before telling that recalbox is just buildroot + ES. Check the api and you will se that none of the rest methods have anything to do with ES.

[neolao]

@eddywebs As indicated by his name, Recalbox API is an API for Recalbox. It doesn't control EmulationStation.

If you look at the documentation, you can modify Recalbox configuration, upload files, create virtual gamepads and launch games.

[slikvik55]

@heydonovan What sort of uses were you thinking of for the API?

[heydonovan]

@slikvik55 Well, for one I think it's silly to have to resort to scraping of any sort. There should be an API that only returns the information needed. Perhaps support for custom box art (from vgboxart.com).

I'm not too sure what else it would need to do. What does the community want? :p