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


Hi Matus,

On Sat, 2012-09-01 at 21:36 +0200, Matúš Kukan wrote:
last time I was merging new libs [0], it was nightmare.

        :-)

I tried too much and then had to keep basegfx, i18nisolang and tl
unmerged because they are used for executables such as rsc and svidl
which are used before libmerged is created, so there would be cyclic
dependencies.

        Oh drat, that is annoying. I wonder if we can create multiple shared
libraries from the same object files to solve that - and link the
build-time tools to those (?).

I think we are ~done with general libraries needed when launching LibreOffice.

        Sounds great - how many did we manage to ram into libmerged ?

I would appreciate if someone could check (review)
https://gerrit.libreoffice.org/#/c/480/

        Looks fine to me :-)

It's a little annoying when you need to do things as
http://cgit.freedesktop.org/libreoffice/core/commit/?id=b4f030f0e3a702e6398698eff08e21141f2c761f
but after gbuild_ure is in master I will probably try to merge
something, once more time. (from stoc/ ..) I assume it is still needed for android ?

        Yes - we're still under significant shlib count pressure on android
sadly; and of course for iOS we'll need to statically link ~everything
into one binary - which is rather more of a fun challenge :-)

        Thanks !

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.