-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rsync for OpenELEC 8 #169
Comments
Why has rsync been removed from unofficial-addons version 8? |
OpenElec 8 has been out for a year. I would assume at this point that there won't be any support for it in the future. I managed to get rsync working though. I will outline this here, it might come in handy for someone else. I cross compiled rsync for armv7 on my regular Linux machine and then copied the binary to my OpenElec box. This workflow is specific for ARMv7 but should be easily adapted for any other architecture. Fetch and unpack the rsync sources:
I installed the ARM GNU Compiler Collection. I'm on Arch and the package is in the AUR:
Initially I had installed:
This only works for ARMv8 though. If you wan't to compile for a RaspberryPIv3 this might be the way to go as this is available as pre-compiled binary while you have to compile the ARM GNU Compiler Collection which took several hours on my machine. Next generate the Makefile:
Then edit the Makefile and replace:
If you want to compile for a different architecture or use another compiler adjust accordingly. To see the architecture you want to compile against, run this on your OpenElec box
Next compile rsync:
Once its done you can check if it compiled for the correct architecture with:
Then create the directory structure and copy over the binary to the OpenElec box:
I then use rsync like this to sync data to the OpenElec box:
|
I have the unofficial-addons enabled, but I can't seem to find
rsync
, orchromium
on OpenElec.I also noticed that there is no git tag in this repo for openelec-8.
Is there a new project superseding this one?
The text was updated successfully, but these errors were encountered: