-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
My (linux) build actually works but I face a stressing situation
Each time I do a git pull -r and then make, then tail_build seems to
build from scratch and takes hours to finish, making my work a PITA.
my autogen is this one:
- --with-num-cpus=4
- --with-max-jobs=4
- --with-vendor=Olivier Hallot
- --enable-graphite
- --with-lang=pt-BR en-US qtz
- --disable-mozilla
I have a I5 machine with 6GB.
I must be missing something... I'll appreciate some advise to make
tail_build compile faster/shorter
Regards
- --
Olivier Hallot
Founder, Board of Directors Member - The Document Foundation
The Document Foundation, Zimmerstr. 69, 10117 Berlin, Germany
Fundação responsável civilmente, de acordo com o direito civil
Detalhes Legais: http://www.documentfoundation.org/imprint
LibreOffice translation leader for Brazilian Portuguese
+55-21-8822-8812
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJP9Cb+AAoJEJp3R7nH3vLxi3IH/0M8rqKzlWqSBq4l98+2DZsu
JVQ7Gz9ZSzT4IruHcrida8kx2MAFJzPO3+jcHch4rfRvwPpNn+1IZiaG4qqWCFQN
F4z49qdyJUc5xYTNoLjCF7zMAnd9r9jydlgM8/h5rXydHa6MqlKSiAREElir1CsP
V5dvqmiZfUZD06G/XcMIJ1qn7tnW7gdI2muGKDYttu//U1pPbDDWCMQ22BS3a/wA
rcDcjxrDSMtnxJ2GvvYfAnCjk/qyChjj997mPPqptdhEy/UnmdCSu5r99gkrUI+d
8k4A3q2uW731/TpYCk2f1O6MQgtSS+ErvO6Ilx+upb2UR5/giIlJvDPHnMYukmw=
=SJFx
-----END PGP SIGNATURE-----
Context
- help with tail_build · Olivier Hallot
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.