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


Hello,

Il 09/09/2012 08:44, Tor Lillqvist ha scritto:
Not sure what we are doing specifically on MacOSX that can break headless.
So there may be more breakage. Fun guaranteed!

Wait, wait. Isn't your motive for this --enable-headless work to be able
to run LO in a headless fashion (document conversions on a Linux or BSD
server would be the typical use case, I guess), without it linking at all
to any X11 or other GUI-related libraries, thus not requiring such packages
to be present at all?

Yeah, building on Linux / BSD without linking to X11 and GUI libs is what is already in git master, It currenctly fails at runtime but that's another story :)

Now, clearly on OS X or Windows there is then no benefit at all in a LO
built with --enable-headless, as the GUI bits of the OS are not "optional"
and always present.

I agree, but being ingenuous i thought that OS X would be enough unix we can build the headless vcl code instead of the aqua code. Building something you can install with brew / macports / whatever. But really if that would require lot of time and pain i'll just add an error in configure for these platforms.

(That the --headless LO option, which is not related to the
--enable-headless configure option, might not work on the Mac, is another
thing. Having that fixed would be good.)

I don't think i have even tried that :)

thanks,
riccardo

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.