I see code review comments like “main branch of core repo is not used for anything. Please port this patch to main branch of online repo and abandon here.” from Andras. I’m confused.
I do not want to work on Collabora online, but to the classic desktop version (the version similar to LibreOffice). I have uploaded my current patch proposal https://gerrit.collaboraoffice.com/c/core/+/3807 by using ./cogerrit submit main .
Is that correct? If not, what do I have to do?
Hi @Regina
There is a nice introduction post from Pedro that explains the new repository setup:
Basically, core is no longer developed as a separate project in the way it used to be. The code now lives under the online repository, and the core is now subtree name engine inside online repo shared with the desktop and online.
I hope that forum post helps clarify the new setup and where patches should be submitted.
Thanks,
Darshan
Latest Collabora Office Classic is built from distro/collabora/coc-26.04.
Command should be `./cogerrit submit coc-26.04`.
That does not work. Message: branch coc-26.04 not found.
What does git branch say? And after `git fetch origin`?
Maybe it is `./cogerrit submit distro/collabora/coc-26.04` sorry I did not try.
From ssh://gerrit.collaboraoffice.com:29418/core
I have started now with a new clone into a new folder git clone ssh://regina-henschel@gerrit.collaboraoffice.com:29418/online I’ve got the files.
And with that a git fetch origin has From ssh://gerrit.collaboraoffice.com:29418/online
But building does not work: I have added an autogen.input file and then $ wsl ./autogen.sh returns Result: All went OK, please run ./configure (with the appropriate parameters) now.
But $ wsl ./configure returns error: header Poco/Net/WebSocket.h not found, perhaps you want to use --with-poco-includes There seems to be something missing or what parameters are needed for configure? How to fix that?
Main issue here is which branch to choose.
`distro/collabora/coc-26.04` mentioned above is the one Classic is built from, and that needs cloning of https://gerrit.collaboraoffice.com/core. But latest Smart Art patches may not be there.
To get those, you may clone gerrit.collaboraoffice.com/onlineand cd into and build only engine inside with GUI so that is runs visible. Building engine is with the same parameters as core or LibreOffice. No build of online would be needed.
In that case, patches still need to be ported to coc-26.04 to be seen in Classic.
Maybe we should think over this.
hi @Regina this will help to solve the POCO error: Build Collabora Office for Linux | Collabora Office - Community Page
Thank you. After building POCO it is now found by configure.
But the next problem arises: Configure does not find node. I’ve installed it for Ubuntu and in the Ubuntu terminal a node -v results v24.16.0. But with wsl ./configure in Git Bash I get the error configure: error: node required to build cool, but not installed
In the meantime, I have installed node in Windows as well. Git Bash now returns /c/Program Files/nodejs/node on which node. And a node -v returns v24.16.0. But wsl ./configure still has checking for node… noconfigure: error: node required to build cool, but not installed
What to do? I only want to build the desktop version.
Hi @Regina
Can you check whether WSL itself can see Node?
wsl which node
wsl node -v
If those work, then Node is available in WSL and the problem is likely elsewhere.
Also, are you building the engine repository or the Online (cool) repository? The error mentions COOL, which suggests the Online build system. For a desktop/core build, Node.js should generally not be the blocker, so it would be helpful to see:
pwd
git remote -v
from the directory where you’re running ./configure.
Thanks
Darshan
No, it doesn’t see Node.$ wsl which node has an empty return and $ wsl node -v returns /bin/bash: line 1: node: command not found
But a $ which node returns /c/Program Files/nodejs/node and $ node -v returns v24.16.0.
Oh, I didn’t know, that I need to go into folder engine to get a desktop build. I’ll try that. At least wsl ./autogen.sh works now (without POCO) and make starts. But stops with errors:
C:colwsl7\online\engine\workdir\UnpackedTarball\boost\boost\optional\detail\union_optional.hpp(600) : error C2220: the following warning is treated as an error
C:colwsl7\online\engine\workdir\UnpackedTarball\boost\boost\optional\detail\union_optional.hpp(600) : warning C4702: unreachable code
make[1]: *** [C:/colwsl7/online/engine/solenv/gbuild/LinkTarget.mk:338: C:/colwsl7/online/engine/workdir/CxxObject/svx/source/diagram/datamodel_svx.o] Error 2
And more problems: After update with ./g pull -r in online, next time wsl ./autogen.sh inside folder engine fails with:
checking Visual C++… ./configure: 13566: ./configure.lineno: vswhere+=\Microsoft Visual Studio\Installer\vswhere.exe: not found
./configure: 1: ./configure.lineno: /mnt/c/PROGRA~2: Permission denied
./configure: 1: ./configure.lineno: /mnt/c/PROGRA~2: Permission denied
checking VC++ Build Tools and similar… ./configure: 1: ./configure.lineno: /mnt/c/PROGRA~2: Permission denied
configure: error: no Visual Studio 2022 installation found