Please Test: Adding support for "All", "Favorites" and "Last Played" systems

cyperghost

@pjft Is it okay for you if I upload the generated binary to github? Or am I breaking laws or a codex by doing this?

Thank you again for providing us with your mod - You made a good job and I appreciate this.

Hex

Ok so those of you who dont know how awesome git is when it does what you want, well here is how you can merge two or more features in different repositories.

Follow these instructions :
Download my script https://github.com/hex007/es-dev/blob/master/es-tests.sh

create and paste / append to es-repos.txt file

https://github.com/pjft/EmulationStation RetroPie-Virtual-Systems-PR

Then create another file es-patches.txt, and paste in it

https://github.com/hex007/EmulationStation feature-powersaver d2aa4861704e4d93659246c13ecc982a6fd18314 Hex's powersaver patch

Run my script and where it asks if you want to apply patches go for yes and select Hex's powersaver patch

And continue with the build.

OR For those comfortable with git only:

git clone --recurse-submodules https://github.com/pjft/EmulationStation -b RetroPie-Virtual-Systems-PR pjft-vs

mkdir pjft-vs/build && cd pjft-vs/build

git  fetch https://github.com/hex007/EmulationStation feature-powersaver
git cherry-pick d2aa4861704e4d93659246c13ecc982a6fd18314

cyperghost

This post is deleted!

cyperghost

@Hex Your way is incredible fast. It takes only 5 minutes to compile. I think it's the make cleanup before. I'm still testing both branches (your and pjft`s)
Thank you :) I will write a small report for favorites usage and CPU usage.

pjft

@cyperghost by all means, feel free to share the binary. I can do it tomorrow as well. My binary was compiled on a pi 3 though.

Sorry for the potentially incorrect instructions, I wrote them from memory.

cyperghost

@pjft de nada

TMNTturtlguy

wow, I travel for work for 2 weeks and the world has turned upside-down! This stuff looks incredible, but I just got a setup that is working wonderfully......I guess i better buy another pi and start a fresh build!

cyperghost

@TMNTturtlguy
There is no need for a second PI... The make process runs wonderfull and you can exchange the compiled binary with the binary in /opt/retropie/supplementary/emulationstation/
Don't worry you won't mess up the system :)

I can provide binaries:
https://github.com/crcerror/emulationstation-binary-archive

Hex

Actually this is a great idea to provide compiled binaries on github with proper versions and features.

cyperghost

@Hex That's a bit hard to handle. I think main feature, author and ES version should be enough.
But everybody is free to fork and add the archive :)
I hope the archive will make development faster and more accurate because more users can simply download and try out versions.

In the repo...

If there is no @ in the name then it's a main branch release within RetroPie
authors of the branch are names by adding @name to the file
main features are named within file name

for ex. emulationstation2.1.5RP means main realase of ES from RetroPie in ES version 2.1.5
for ex. emulationstation2.2.4RP PS @hex PowerSavingsmeans ES branch from @hex with PowerSaving feature with ES version 2.2.4

Hex

@cyperghost said in Please Test: Adding support for "All", "Favorites" and "Last Played" systems:

@Hex That's a bit hard to handle. I think main feature, author and ES version should be enough.
But everybody is free to fork and add the archive :)

I mean for a tester to do and not the developer. The dev cannot keep on sharing the binaries as they are much busy compiling

cyperghost

Added @pjft file to binary archive RPI2/3 only

https://github.com/crcerror/emulationstation-binary-archive

How to:

Copy file from repro and rename it back to emulationstation
Rename file emulationstation in /opt/retropie/supplementary/emulationstation/ maybe emulationstation.org >> That's your backup!
Copy repro file to /opt/retropie/supplementary/emulationstation/
User rights 755 root:root

@Hex I wans't able to merge your Powersaver Patch together with @pjft
I added

https://github.com/hex007/EmulationStation feature-powersaver d2aa4861704e4d93659246c13ecc982a6fd18314 Hex's powersaver patch

to es-patches.txt but I wasn't able to select this patch. Just the Repro was available.

meleu

@Hex hey bro, do you recommend some cross compiling guide? Compiling ES on my raspi1 is very time consuming and on my laptop take 2 or 3 minutes. I compiled the very first version of the @pjft 's PR and it took almos 4 hours on my raspi1. Now I don't have the guts to compile the new changes we are getting (I would like to test/provide feedback about two PRs you submitted too).

cyperghost

@meleu Maybe I uploaded the file you need already.
https://github.com/crcerror/emulationstation-binary-archive

--

Sorry @pjft your branch work wonderfull. I can even favourize the favourites of Little Favourite Launcher and it works flawless ;) Thank you very much I'm looking forward that the next release will be a burner :)

One suggestion. The "Added xxxxx to favourite" beacon is in the middle of the upper screen. May you can set it to right down corner?

Little Bug if you add a Favorite within the auto-favorite then ES will give error message segmentation faultand the binary is killed

Hex

@meleu Thats the beauty i work with. I write all my code on my linux system only. I test it on rasp pi only when i reach a workable copy. skipping make clean should reduce the compile time. The thing is the higheryour changes are in the hierarchy the more files are compiled again. If you have a Pi3 i would suggest compiling on that. It is fast on pi 3. Use 2 or 3 cores only and not all 4 else you will run out of ram.

I do not have a cross compile setup. I never have used one.

Hex

@cyperghost Did you atleast see the patches menu?

 es-dev.sh (version: zeta.2) - manage EmulationStation mods on your RetroPie
 ────────────────────────────────────────────────────────────────────────────

┌─────────────────────────────────────────────────────────────────────────┐
│ Would you like to apply any patches from es-patches.txt or remove all   │  
│ patches applied to this repository?                                     │  
│                                                                         │  
│                                                                         │  
│                                                                         │  
│                                                                         │  
│                                                                         │  
│                                                                         │  
│                                                                         │  
│                                                                         │  
│                                                                         │  
├─────────────────────────────────────────────────────────────────────────┤  
│                       < Yes >            < No  >                        │  
└─────────────────────────────────────────────────────────────────────────┘

cyperghost

No... This windows I had never seen.

I tried manually via the github commands you posted... But then there was an error message about the cherry pick, that I can't commit the file.

git clone --recurse-submodules https://github.com/pjft/EmulationStation -b RetroPie-Virtual-Systems-PR pjft-vs

mkdir pjft-vs/build && cd pjft-vs/build

git  fetch https://github.com/hex007/EmulationStation feature-powersaver
git cherry-pick d2aa4861704e4d93659246c13ecc982a6fd18314

git clone works and downloads pjfts branch
of course works
git fetch also works
did not work

Hex

@cyperghost please post the error that you get.

cyperghost

from git fetch https://github.com/hex007/EmulationStation feature-powersaver

pi@retropie:~/pjft-vs/build $ git  fetch https://github.com/hex007/EmulationStation feature-powersaver
From https://github.com/hex007/EmulationStation
 * branch            feature-powersaver -> FETCH_HEAD

from git cherry-pick d2aa4861704e4d93659246c13ecc982a6fd18314

pi@retropie:~/pjft-vs/build $ git cherry-pick d2aa4861704e4d93659246c13ecc982a6fd18314
error: Your local changes would be overwritten by cherry-pick.
hint: Commit your changes or stash them to proceed.
fatal: cherry-pick failed

Hex

@cyperghost Okay i get what is happening. follow these commands and post on success or failure (post error messages too mate)

git cherry-pick --abort
git reset --hard
git cherry-pick d2aa4861704e4d93659246c13ecc982a6fd18314