[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-2d-dev
Subject:    [OpenJDK 2D-Dev] Fw: [PATCH] Allow linking in (shared) libfontconfig directy
From:       flameeyes () gmail ! com (Diego 'Flameeyes' =?UTF-8?B?UGV0dGVuw7I=?=)
Date:       2007-05-22 20:42:58
Message-ID: 20070522224258.616bcce7 () enterprise ! flameeyes ! is-a-geek ! org
[Download RAW message or body]

Hi,

On Mon, 21 May 2007 15:40:54 -0700
Phil Race <Phil.Race at Sun.COM> wrote:
> I could construe this either way. If its almost free it doesn't
> matter if you do even if you don't need it, or if you do it twice.
Right, this is why I suppose an option wouldn't be a bad idea :) Leave
it up to either user or distribution to choose between the two at build
time (in case of Gentoo, it would most likely become an useflag, I
suppose).

Oh by the way t here is one case where the direct link would be safer:
if fontconfig's ABI changes, but the API doesn't, dlopen would be a
problem, while direct linking would resist just fine. Of course we all
hope that this will not happen (I'm scared to think about
the widespread breakage due to a change in libfontconfig changing
ABI).

-- 
Diego "Flameeyes" Petten?
http://farragut.flameeyes.is-a-geek.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.openjdk.java.net/pipermail/2d-dev/attachments/20070522/4d10ac2a/attachment.bin 

[prev in list] [next in list] [prev in thread] [next in thread]