On Tuesday 18 of February 2020, Michael Stahl wrote:
On 17.02.20 22:03, Luboš Luňák wrote:
But the same can be said about system Python on Linux, no? So where's
the difference?
--enable-python=system is a configuration that only distro packagers
should use, after verifying that the system Python does provide
everything LO requires.
I've been using it for ages too, and it just works for me. And I'm willing to
bet it'll just work for Windows Jenkins builds too.
it's not possible to distribute such LO builds
This is not about distributing anything:
On Sunday 16 of February 2020, Luboš Luňák wrote:
It would make sense to have some --with-system-libs=auto which would try to
use as much system stuff as possible and print a summary,
and --enable-debug/dbgutil could default to it. Even on Windows, e.g.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
python3 is an optional component installed by MSVC, I don't know why we
don't even try to use it.
--
Luboš Luňák
l.lunak@collabora.com
Context
- Re: Tracing where build time is spent (continued)
Re: Tracing where build time is spent · Stephan Bergmann
Re: Tracing where build time is spent · Michael Stahl
Re: Tracing where build time is spent · Jan-Marek Glogowski
Re: Tracing where build time is spent · Jan-Marek Glogowski
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.