Which linux distribution(s) are Linphone developers primarily using to compile each sub-package stand alone, such as done at OBS Build Service? It might help to know which linux distribution to start adapting when upgrading to newer versions.
The following distributions seems to have compiled better on OBS Build Service with few adaptations needed:
Raspbian 12
Debian 12 (suspected dev-system)
Debian Sid
Ubuntu 22.04 (suspected dev-system which would also work for Linux Mint)
Ubuntu 23.10
openSUSE Tumbleweed
Fedora 39 (suspected dev-system)
Fedora 38 (suspected dev-system)
Archlinux
Manjaro
OBS Build Service has difficulties to compile linphone-desktop v5.2.0 on all linux distributions.
It seems that the build file(s) only look for libraries in one (or a very few) locations, although all libraries are present on the system (build as separate packages and installed in usr/...).
.../external/ispell is empty directory and missing CMakeLists.txt which makes cmake complain. There is no cmake -DENABLE_ISPELL=OFF option available to deactivate compilation of ispell as there is for disabling qt-keychain compilation (seems not to compile well on OBS Build Service).
Find<library>.cmake files seem to look for the .cmake files with slightly different names (lower case to mixed case in file names introduced, example: bctoolboxConfig.cmake => BCToolboxConfig.cmake) and seems not to look in all GNU lib directories on the system. It seems that Find<library>.cmake only looks in a build-subdirectory where the bundled files typically would be discovered and skips looking in /usr/... directories where the .cmake files are installed by the various dependency-packages already compiled previously.
General information
Device: Linuxbox
OS:
Raspbian 12
Debian 12 (suspected dev-system)
Debian Sid
Ubuntu 22.04 (suspected dev-system which would also work for Linux Mint)
Ubuntu 23.10
openSUSE Tumbleweed
Fedora 39 (suspected dev-system)
Fedora 38 (suspected dev-system)
Archlinux
Manjaro
Version of the App: 5.2.0
Version of the SDK: corresponding
Expected behaviour
Expecting successful compilation on OBS Build Service.
To Reproduce
Overview to see what probably currently compiles on OBS Build Service and what currently probably does not compile yet, with margin for errors:
Context
First, a general inquiry:
Which linux distribution(s) are Linphone developers primarily using to compile each sub-package stand alone, such as done at OBS Build Service? It might help to know which linux distribution to start adapting when upgrading to newer versions.
The following distributions seems to have compiled better on OBS Build Service with few adaptations needed:
OBS Build Service has difficulties to compile
linphone-desktopv5.2.0 on all linux distributions.It seems that the build file(s) only look for libraries in one (or a very few) locations, although all libraries are present on the system (build as separate packages and installed in
usr/...)..../external/ispellis empty directory and missingCMakeLists.txtwhich makes cmake complain. There is nocmake -DENABLE_ISPELL=OFFoption available to deactivate compilation ofispellas there is for disablingqt-keychaincompilation (seems not to compile well on OBS Build Service).Find<library>.cmakefiles seem to look for the .cmake files with slightly different names (lower case to mixed case in file names introduced, example:bctoolboxConfig.cmake=>BCToolboxConfig.cmake) and seems not to look in all GNU lib directories on the system. It seems thatFind<library>.cmakeonly looks in a build-subdirectory where the bundled files typically would be discovered and skips looking in/usr/...directories where the .cmake files are installed by the various dependency-packages already compiled previously.General information
Expected behaviour
Expecting successful compilation on OBS Build Service.
To Reproduce
Overview to see what probably currently compiles on OBS Build Service and what currently probably does not compile yet, with margin for errors:
software.opensuse.org/package/linphone-desktop
OBS Build Service Monitor
Additional context
No response
SDK logs URL
No response