libretro
"Nightly" Libretro Buildbot cores for armhf and armv7-neon-hf are 2.5 years old
It appears that the "nightly" builds at https://buildbot.libretro.com/nightly/linux/armv7-neon-hf/latest/ and https://buildbot.libretro.com/nightly/linux/armhf/latest/ aren't getting built (at least according to their timestamps). If those timestamps are accurate, it means anytime you use RetroArch's online updater to update cores on a Raspberry Pi 4, you're getting cores that are 2.5 years old.
Yep, that's true. There is a github repo that hosts up-to-date builds for those arches here: https://github.com/christianhaitian/retroarch-cores
but we can't speak for the integrity of them, so it would be irresponsible to just copy/paste them into the online updater for distribution, unfortunately.
I have also compiled some cores that are available for download: https://zoltanvb.github.io/armv7-hf-neon/
I have also compiled some cores that are available for download: https://zoltanvb.github.io/armv7-hf-neon/
Not work, In retroarch for miyoo is empy.
I have also compiled some cores that are available for download: https://zoltanvb.github.io/armv7-hf-neon/
I've tried your flycast_libretro, it does not work right now (goes back to EmulationStation on Retropie)
I have also compiled some cores that are available for download: https://zoltanvb.github.io/armv7-hf-neon/
Not work, In retroarch for miyoo is empy.
Which model? Actually for miyoo, there are cores on the buildbot, such as: http://buildbot.libretro.com/nightly/dingux/miyoo-arm32/latest/
I have also compiled some cores that are available for download: https://zoltanvb.github.io/armv7-hf-neon/
Not work, In retroarch for miyoo is empy.
Which model? Actually for miyoo, there are cores on the buildbot, such as: http://buildbot.libretro.com/nightly/dingux/miyoo-arm32/latest/
But this is for old miyoo models, the last model (mini and mini plus) work with armhf.
Yep, that's true. There is a github repo that hosts up-to-date builds for those arches here: https://github.com/christianhaitian/retroarch-cores
but we can't speak for the integrity of them, so it would be irresponsible to just copy/paste them into the online updater for distribution, unfortunately.
can't speak to the integrity of them in what way?
Just that we didn't build them so we can't guarantee they haven't been tampered with, etc. I'm not saying that to cast aspersions, just explaining why we can't ethically distribute them ourselves.
@hizzlekizzle can we get any more information on this? I'd like to get these builds updated (and have generic aarch64 builds added officially). Willing to assist where possible.
