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


You are looking for autogen.sh.

Look at a log on Jenkins (not Gerrit) and find the parameters passed to
autogen.sh. You'd need to customize a couple of them (junit and ant, which
you must download and place somewhere on your system and give the path to
autogen.sh).

For reference, here is mine (it's called from a config.sh a directory above
'libo' which is the root of the code). This will build full debug and will
generate ~27GB:

DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )
$DIR/libo/autogen.sh --with-junit=$DIR/junit-4.10.jar
--with-ant-home=$DIR/apache-ant-1.9.4 --with-visual-studio=2013
--with-parallelism=24 --enable-sal-log --enable-dbgutil --enable-debug
--disable-odk --enable-pch --disable-ccache

On Thu, Jul 16, 2015 at 5:55 AM, Giuseppe Castagno <
giuseppe.castagno@acca-esse.eu> wrote:

Hi all,

I'd like to prepare home a Win7 machine to build LibO with a configure
script as the one used by gerrit builds.

What will it be the most current configure to use?

Looking at the log available, it seems that a prepared set of shell
variable is used, what configure generated it?


Thanks

--
Kind Regards,
Giuseppe Castagno aka beppec56
Acca Esse http://www.acca-esse.eu
giuseppe.castagno at acca-esse.eu
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


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.