Subject: Request for Step-by-Step Guide to Run Collabora Online Locally on my machine Ubuntu 24.0
I need some clarification regarding my specific requirements.
My Requirements:
- Local Development: I want to run Collabora Online(both backend and frontend) on my local machine using Ubuntu 22.04.
- Source Code Modifications: My goal is to make changes to the source code and observe these changes on the UI to better understand the codebase and contribute effectively.
Request:
Could you please provide a “step-by-step guide” or direct me to a “detailed document” that outlines how I can achieve this? Specifically, I need to know:
- Which repository I should clone for running the backend and frontend together?
- The exact steps to get Collabora Online running on my local machine.
- How to make changes to the source code (e.g., UI changes) and see those changes reflected when I run the application.
I’m using Ubuntu 24.0 and have experience with Node.js, JavaScript, and React.
till now i have cloned Collabora Online repository and run ./autogen.sh after this i had run ./configure but getting some error or dependency here are my terminal output after configuration
sarv@sarv-Latitude-5490:~/online$ ./configure
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking for gawk... no
checking for mawk... mawk
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking whether make sets $(MAKE)... yes
checking whether make supports the include directive... yes (GNU style)
checking whether make supports nested variables... yes
checking how to create a pax tar archive... gnutar
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking dependency style of g++... gcc3
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking whether ln -s works... yes
checking for lxml for python3... yes
checking for polib for python3... yes
checking for the need of -latomic... No
checking whether to enable debug build... no (Release build)
checking if ssl verification is enabled by default... true
readlink: missing operand
Try 'readlink --help' for more information.
checking for vendor... not set, using sarv
checking for custom icon theme... no
./configure: line 19472: linux-gnu: command not found
checking whether to turn warnings to errors... yes
checking whether to use extra compiler hardening flags... yes
checking whether gcc supports -grecord-gcc-switches... yes
checking whether gcc supports -D_FORTIFY_SOURCE=2... no
checking whether gcc supports -D_GLIBCXX_ASSERTIONS... yes
checking whether gcc supports -fstack-protector-strong... yes
checking whether gcc supports -fstack-clash-protection... yes
checking whether gcc supports -fcf-protection... yes
checking whether code-coverage is enabled... no
checking whether to build fuzzers... no
checking whether to turn sanitizers on... no
checking whether g++ supports C++20... yes (-std=c++20)
checking whether the compiler is clang... no
checking for LibreOffice path... not found
configure: error: LibreOffice path must be configured: --with-lo-path
my goal is to run it on my machine successfully and make some changes in it and observe changes in UI later i will try to integration with my dummy project for understanding
Your guidance would be greatly appreciated as it will help me contribute to the project and understand the codebase more effectively.
Thank you in advance for your support!
Best regards,
sumit singh