What command line options? The same SAL_LOG environment variable is
usable, just like on Linux and Windows. You just have a build that has the
logging code compiled in. (I.e. either built with --enable-sal-log,
--enable-debug or even --enable-dbgutil. Normal production builds don't
have it.) Use like this, for instance, to get the output from SAL_INFO()
calls with the tag "sw" but no warnings.
I normally work with versions compiled with —enable-debug, which give me
plenty of debug.
Thanks for pointing me in
the right
direction
I cannot recognise your timing, on my mac the example takes far less than a
second.
I've created a bug and attached a video demonstrating the issue
https://bugs.documentfoundation.org/show_bug.cgi?id=106154
Thanks,
Adomas
Context
Re: Various MacOS extension issues. · Stephan Bergmann
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.