I got it to compile (had a heck of a time getting all the dependencies, and for the life of me, I don’t know why it had a problem with zlib-dev… but eventually, after installing some completely unrelated package, it suddenly could find zlib…
anyway, it built, but when I try to install, kodi doesn’t seem to like the zip file…
While backtracing I discovered that the Vero4k+ (or OSMC in general?) has a repository addon with ID “repository.xbmc.org” which references download.osmc.tv instead of mirrors.kodi.tv (which I think is the default Kodi repository for mentioned ID, at least it is on Windows). I understand that OSMC has it’s own addons to provide/update, but couldn’t that be done more transparently by adding another repo with a different ID just for those addons? I’m just a newbie trying to understand all this and I first suspected that the different repository was the cause of certain addons not being available.
@randallspicher Can you share your build of the addon? Or would a build for Vero3 not work on a Vero4k+? Aren’t they both AARCH64?
If I remember correctly, there are problems with these add-ons for non Windows platforms. But I’ll see if they can be reintroduced now.
The Kodi repository doesn’t provide ARM binary add-ons, so even if you switch to the Kodi repository, this won’t help. We still use the Kodi repository ID to prevent problems with add-ons which depend on the Kodi repository, but we change the URL to reduce bandwidth on Kodi infrastructure. The repository is identical in content to the Kodi repository and just has a different name for cosmetic purposes.
@sam_nazarko I’m sorry this post is not contributing to the thread but Sam, but I can’t let this go unsaid: the swiftness of your reply and how accurate and correctly it addresses my question is something I don’t see very often. Your qualities really show, keep up the good work!
Thanks for considering adding them back. No problem if it’s on the low prio list , can imagine there are more important matters.