Hi Matus,
On Mon, 2011-10-10 at 20:22 +0200, Matúš Kukan wrote:
I just realized (although it's quite basic thing... I was never
thinking more about details of this merging thing)
that we can't merge anything what we would want.
Sure - we have to merge sets of inter-dependent libraries.
For example we have libraries linking chain:
svx -> drawninglayer -> cppcanvas -> canvastools
In list of always used libs (when using writer, calc... ) is svx and
canvastools so we'd like to merge them but we can't because we'd get
linking dependency cycle.
Yep - we have to chuck them all into one big library. Luckily - since
they all depend on each other - we would have them all linked into core
anyway: so we can only win doing that.
So what is the best strategy now ? Try to merge as much as possible ?
Or carefully choose each one?
Well - I guess we should draw a line around some big chunk including
svx (a big beast), and link it all together: clearly we'd need to ensure
the UNO factory functions are disambiguated.
Maybe it's better to merge more.. but I'm not sure about this.
The ultimate aim is to merge as much as possible to give the link-time
optimiser the best view of everything I think ...
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.