Fresh OSMC install from USB stick. Git checkout of May tag and make vero5 in the mediacenter-osmc package.
OSMC mediacenter build for Vero 5 fails for me during the binary addons step:
CMake Error at cmake_install.cmake:54 (file):
file INSTALL cannot find <path>/2048_libretro.so: No such file or directory
make[3]: *** [Makefile:137: install] Error 1
make[2]: *** [CMakeFiles/2048.dir/build.make:93: 2048/src/2048-stamp/2048-install] Error 2
make[1]: *** [CMakeFiles/2048.dir/all] Error 2
The 2048 addon compiles cleanly but outputs 2048_libretro.dll (Windows DLL) instead of 2048_libretro.so. The cmake install step then can’t find the .so and aborts.
Potential Root cause:
The libretro 2048 addon’s CMakeLists.txt contains:
elseif(CORE_SYSTEM_NAME STREQUAL linux)
if(CMAKE_SYSTEM_PROCESSOR MATCHES "aarch64|arm64")
set(PLATFORM unix-aarch64)
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^arm")
set(PLATFORM unix-neon)
else()
set(PLATFORM unix)
endif()
On Vero 5, CMAKE_SYSTEM_PROCESSOR=armv7l matches ^arm, so PLATFORM=unix-neon. CMake then invokes make platform=unix-neon on the bundled Makefile.libretro.
That Makefile seem to have no unix-neon case. Known platforms are unix, linux-portable, osx, ios-arm64, tvos-arm64, qnx, emscripten, and various consoles. An unrecognized platform= value falls through to the Makefile’s default branch, which produces Windows-style .dll output.
I tried to patch it in the build.sh file. But it never worked right.
Yeah, I am bit lost in the makefile + build/sh + ../common.sh + ../../scripts/common.sh chain that is chrooted an then goes Kodi CMake, and what belongs to what. It’s hard to track issues with multi threaded compiling down the chain, that always starts from scratch. So a bit lost here how to fix the issue.
And advise?