On Thu, 2012-03-29 at 20:43 +0100, Caolán McNamara wrote:
On Thu, 2012-03-29 at 16:56 +0200, Lubos Lunak wrote:
Is there any need to run UI stuff during build? IOW, can't we simply globally
force using headless for everything during build?
Unix has the env SAL_USE_VCLPLUGIN=svp which would force headless mode.
Though I don't think macosx or windows honors that, hence the --headless
Right.
I'm not sure why e.g. the fairly simple hwpfilter test, or any of them
really, would end up triggering anything UI-related. I guess there might
be some painful-to-fix assumption somewhere that tries to create a
dialog or render some text into a drawable and want to query the
desktop-settings for the default fontoptions on the system or some such
which cascades out of control.
So - unfortunately on Windows & Mac we initialize VCL for those tests
which I imagine creates an invisible window (for it's event loop) and
other more or less evil & non-desired stuff.
Having said that, it normally doesn't popup dialogs and shouldn't
interfere with the UI - what are you seeing ?
The main reason (IIRC) is that the font logic is not available outside
of the unix / freetype world and that is needed for the headless /
generic code, and until we either split out the font handling to be
better abstracted, or ship freetype cross-platform we'll have to do this
way I IIRC.
Work appreciated to improve the vcl/generic split etc. :-)
HTH,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
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.