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


Hi Michael, Tor

On 17 February 2012 18:36, Michael Meeks <michael.meeks@suse.com> wrote:
       Well, I'm building and running with it myself on Linux; so far it seems
that libmergedlo.so is only 5.1Mb - which surprises me, since my libsvx*
are both rather huge.

It has ~28 MB for me now.

       As/when we have really a lot of code in there, I was going to poke Jan
H. again to see if we could borrow some more of his cycles wrt. LTO on
it - but for that I'd like to have something impressive ;-) "world's
biggest shared library" is nearly that (perhaps).

       Anyhow - that was my plan ;-)

:) nice
So, I have added more and fixed component dependency issue with
http://cgit.freedesktop.org/libreoffice/core/commit/?id=b1a87ca7840ab4ed17e8a775fcd4726c2fc5b75d

But I am not able to build LibreOffice with recent gcc 4.7. I don't
know if the problem is in gcc, LibreOffice or me.
It fails in testtools/source/bridgetest/ and I think also later in
some unittests.

       Thoughts ?

Maybe we could add also vcl ? Its makefile is ugly but it's quite large.
When I tried it I got multiple definitions of 'main' in:
desktop/source/app/main.o
svx/source/dialog/sendreportunx.o

And do we still want only libraries needed at start there ?
Maybe we could merge fwm and fwl only for Android and I guess more can
go there in Android, not start-library case too.

Matus

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.