I'm trying to build version 5.2.3.1 (git commit 01ec8f357e) for the android viewer. When doing so, I get the error: In file included from libreoffice-core/desktop/source/app/opencl.cxx:31:0: libreoffice-core/include/opencl/openclwrapper.hxx:16:23: fatal error: clew/clew.h: No such file or directory #include <clew/clew.h> ^ compilation terminated. libreoffice-core/solenv/gbuild/LinkTarget.mk:189: die Regel für Ziel „libreoffice-core/workdir/CxxObject/desktop/source/app/opencl.o“ scheiterte make[1]: *** [libreoffice-core/workdir/CxxObject/desktop/source/app/opencl.o] Fehler 1 make[1]: *** Auf noch nicht beendete Prozesse wird gewartet … Makefile:256: die Regel für Ziel „build“ scheiterte make: *** [build] Fehler 2 configure.ac tells me that clew is not supposed to be used on Android, which probably means the file is included erroneously. When I remove that file the compilation continues, until it bumps into two other build errors about opencl. They required me to do two additional changes: 1. adapt the about dialog to exclude opencl (it included a file and called a method from it) 2. remove a line with "desktop/source/app/opencl" from desktop/Library_sofficeapp.mk I am working towards getting it included with those changes, but it would be nice if these changes could be upstreamed, so that future versions of libreoffice don't require them. Obviously, one would need to do something more sensible than deleting files or lines. This is a problem I discovered when building libreoffice for f-droid (Bug 103067).
Hello LibreOffice guys, first I'd like to say I really appreciate effort on developing LibreOffice. Second, I'd like to ask, as F-Droid user, if you could give a hand for people who building LibreOffice for F-Droid. It would make process much easier and faster :) Also it would reduce number of bugreports about outdated LO in F-Droid. Thank you
Christian, do you remember if clew was breaking Android build on master, and how it was fixed?
Hello guys, Any progress? I noticing that F-Droid maintainer is not able to build new LO builds, so if would be possible to look at this (and other build) issue, that would be great :) Thank you
Hi David, I'd expect this issue to be gone in 5.3, has the maintainer tried recently, and if they did, what is the error currently?
Let's assume this bug is fixed, and if there is a different issue, a new report should be opened on that.