To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=65521
                  Issue #:|65521
                  Summary:|statically link freetype to vcl ...
                Component:|gsl
                  Version:|680m167
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|PATCH
                 Priority:|P2
             Subcomponent:|code
              Assigned to:|pl
              Reported by:|mmeeks





------- Additional comments from [EMAIL PROTECTED] Thu May 18 02:23:03 -0700 
2006 -------
So - there is a problem.

Many systems' gtk+ (and Qts) require / link to a newer freetype. This code
expects freetype to export symbols such as FT_GlyphSlot_Embolden (eg.) It also
(most likely) expects a different ABI.

When we fiddle LD_LIBRARY_PATH and include our own libfreetype before we then
dlopen system libraries (eg. gtk+/cairo) expecting the system freetype [ which
has more symbols / different behavior ] all hell breaks loose: things crash,
fail to link, mis-function etc.

The *simplest* solution to this [ based on the fact that only libvcl680li.so
actually wants it's own (internal) freetype - cf.

$ for a in *.so; do echo "Lib $a"; objdump -p $a; done 2>&1 | less

whereas all other DT_NEEDEDs are (in fact erroneously, but ... ;-) inherited
from the system.

We *should* statically link our own libfreetype into VCL, and not install our
own version: this has the following benefits:

* fix <N> crasher bugs / system integration problems
* faster linking / startup time
* code size reduction: linker can remove dead sections etc.

So - the patch (yes this isn't really a patch bug) is rather trivial.

Of course, this doesn't affect Novell's (or most Linux) builds, only the
up-stream / system builds. [ Although it affects us because we want to upgrade
the internal freetype at some stage to use these new features without
de-stabilizing thigns ].

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to