Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


 That's quite normal, you've read README.cross ? :-) also more concrete
details on the specific problems would be good.

Also, http://www.iki.fi/tml/libocon2011-xcompiling.pdf gives an
overview of LibeOffice cross-compilation in general.

I've had some difficulty building it.

Please give more details. (On this list, not in private mail.)

The master branch is obviously a moving target. For a month or so I
haven't attempted iOS compilation, so some slight problem might have
popped up.

(I just tried to run autogen.sh for iOS and indeed noticed a problem
in the checks for libxslt. Will fix up that.)

 Tor's also doing some nice work to shrink what is compiled and included
by adding a DESKTOP flag that is not set [when compiling for] these devices - to shrink
the big blob

Well, the DESKTOP flag is more to just avoid wasting time on compiling
completely unnecessary "modules"--- also in the parts that do get
compiled now there surely is lots of stuff that doesn't make sense on
portable devices.

 Finally some small amount of wrapper logic to run the moral equivalent of:

       ./soffice --convert-to pdf foo.docx

Yup. Something like that should be doable relatively soon, as the
LibreOffice code obviously for such usage doesn't display anything or
require any interactive input. But all the C++ and UNO stuff still
needs to work, of course, and there is lots to do there.

--tml

Context


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.