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


On 26/11/13 10:49, Mohamed-Ali BEN MANSOUR wrote:

Hi everyone,

I was building LO 4.1 version and i've found this option in
distro-configs\LibreOfficeWin32.conf:
--enable-win-mozab-driver

According to the wiki:
https://wiki.documentfoundation.org/Development/Windows_Build_Dependencies#Install_Windows_Build_Requirements
, Mozilla build tooling is only used for LibreOffice versions older than
4.1.

that is true, but...

I propose to remove this option from the file (LibreOfficeWin32.conf)..

... what it actually means is that in contemporary releases it's no
longer possible to build the mozilla stuff from source (hence no need
for the tools); what --enable-win-mozab-driver does instead is to
download and unpack pre-built binaries and put them into the
installation set.

of course if we had somebody implement native Outlook / Outlook Express
address book driver we could remove that too :)

We also need to modify the autogen.lastrun for builds at this link:
http://dev-builds.libreoffice.org/daily/libreoffice-4-1/Win-x86_9-Voreppe/2013-11-11_21.19.15/libreoffice-4-1~2013-11-11_21.19.15_build_info.txt
Actually, we have in the same file: "--enable-win-mozab-driver" and 
"--disable-win-mozab-driver"

that is indeed funny to have both of these in there.

By the way, is it normal that we can't see any build in this directory:
http://dev-builds.libreoffice.org/daily/libreoffice-4-1/Win-x86@42 ?

that's a good question - Thorsten, why isn't Win-x86@42 doing uploads?

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.