Hi guys,
I've been investigating a possibility of LibreOffice cross-compilation for Linux X-less device(ARM)
and use it as document(writer/calc/impress) to pdf converter.
1) Is it possible to compile LO without any graphic library (pure -headless)? Or how much work
would that require?
2) Is it possible to eliminate all unnecessary libs and resources? They're using valuable
device resources and may cause compilation problems. Anybody knows how small would it get with
minimal subset of libs?
3) Also I've found that in UNO docs:
"A long term target on the OpenOffice.org roadmap is to split the existing OpenOffice.org into
small components which are combined to provide the complete OpenOffice.org functionality. [..]When
this target will be reached, the API, the components and the fundamental concepts will provide a
construction kit, which makes OpenOffice.org adaptable to a wide range of specialized solutions and
not only an office suite with a predefined and static functionality. "
This sounds like what we need. Do you know how far it got yet?
4) Are the libraries loaded on demand by soffice process or they need to be reachable at the
start? If they would be demanded on load it would give us opportunity to remove unnecessary libs.
5) If we're about hacking the build process to our needs (removing dependencies) where should
we start?
Andrzej Pacanowski
Context
- [Libreoffice] PDF converter cross compilation general questions · Andrzej.Pacanowski
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.