I'm trying to build LO 6.1.6 (gcc 4.9 armv7hl) with no GUI. I need LO
functionality of parsing different files (including text, tables and
presentations) and rendering it to png. So, I've configured build
./autogen.sh --without-help --without-myspell-dicts --disable-gtk3
--disable-gtk --disable-gui --disable-kde4 --disable-dbus
--without-doxygen --disable-report-builder --disable-coinmp
--disable-odk --disable-cups --disable-lotuswordpro --without-java
--without-krb5 --disable-scripting-beanshell
--disable-scripting-javascript --disable-sdremote
--disable-postgresql-sdbc --without-fonts --with-parallelism=4
--with-system-boost --with-system-nss --disable-firebird-sdbc
--with-system-hunspell --with-system-libatomic_ops
--with-system-librevenge --with-system-epoxy --with-system-libmwaw
--with-system-icu --with-system-graphite --with-system-harfbuzz
--with-system-libpng --with-system-cairo --with-galleries=no
--enable-cairo-canvas --with-system-zlib --without-junit
then make it, but when I'm trying to run ./soffice.bin --convert-to pdf
test.doc or use lok::lok_cpp_init from LibreOfficeKit, an error occures:
*LibreOffice - dialog 'LibreOfficeDev 6.1 - Fatal Error': 'The application
cannot be started.*
Little debugging through code gave me a clue, that it's might be unability
to initialize UNO or just setting wrong PATH\LD_LIBRARY_PATH\etc.
So, what am I doing wrong? (except using --disable-gui, I've seen, it's
experimental)
Context
- Cannot start LO with --disable-gui build · Alex Kom
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.