Le Wed, 21 Nov 2012 17:33:20 +0100, <d.ostrovsky@idaia.de> a écrit:
Quoting Stephan Bergmann <sbergman@redhat.com>:
Further clean-up of all the Mozilla-related configure switches
(--enable-mozilla, --disable-build-mozilla, --with-mozilla-toolkit,
--with-system-mozilla, --with-mozilla-build) and config_host.mk.in
variables (BUILD_MOZAB, DEFAULT_MOZILLA_TOOLKIT, MOZILLABUILD,
MOZILLA_VRESION, MOZ_FLAVOUR, MOZ_INC, MOZ_LIB, MOZ_LIB_XPCOM,
PREBUILD_MOZAB, SYSTEM_MOZILLA, WITH_MOZILLA), which should all now be
relevant for Windows only, is highly appreciated.
the only option that would stay forever (even after dropping the whole
mozilla mess from the build tree) is --with-mozilla-build. It is used
for nss to provide some build tools. I suggest to rename this option to
--with-nss-build or something like that (without name mozilla in it).
David
Am going for it.
--enable-mozilla now means enable mozilla address book driver on windows
--with-mozilla-build will be renamed to --with-nss-build (although nss is
coming from mozilla, and then, we still downlaod from mozilla.org :)
--with-nss-build is required on windows if --enable-mozilla is on and
--with-system-nss is off.
Other switches and related variables will be cleaned.
IIUC, with_system_nss = yes is used for all but Win [1]. Could we try to
use the ones provided with any install of firefox under windows ?
Regards
[1] : http://opengrok.libreoffice.org/xref/core/configure.ac#8215
--
Mat M
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.