Problems running Swing app with latest build?
philip.race at oracle.com
Tue Feb 14 11:42:32 PST 2012
Let me cut through some of the noise and confusion.
The Oracle JDK for OS X product will not (does not!) require freetype.
We "bundle" a different rasteriser (t2k) for the few cases that the OS X
JDK 7 will need it.
Mostly embedded font support and Type 1 font support.
So no end user will suffer from this error if they use our builds nor do
they need to
So Greg should be building using that closed source rasteriser if he
wants to avoid
this issue. I can tell him what to do offline.
OpenJDK builds (no closed components) for OS X however do depend on
because they don't get that closed source rasteriser.
This isn't a dependence on X11 APIs, but it is true that X11 is what
packages up freetype.
The bug 7124341 is low priority because its NOT an issue for the Oracle
And probably is not easily fixable other than by installing the right
corresponded to whereever you got your openjdk binary. I am not sure how
this could ever happen if you are building openjdk on your own system except
maybe if you update X11 without rebuilding JDK afterwards.
On 2/14/2012 10:52 AM, Roger Lewis wrote:
>>> On 2/13/2012 10:22 PM, Mike Swingler wrote:
>>>> As a general point, the JDK 7 on the Mac should not be linking
>>>> against libfreetype in the first place, because it's an X11
>>>> component, and optionally installed on Mac OS X. If there isn't a
>>>> bug already to this effect, I'd be more than happy to file it.
>>> FreeType is not an X11 component, it's a font manipulation library
>>> ("a software font engine" ). OpenJDK requires FreeType even on MS
>>> Windows platform, so this requirement is unlikely to go away.
>>>  http://www.freetype.org/freetype2/index.html
>> On Mac OS X, it is delivered with X11, which is an optionally
>> installed component. If OpenJDK requires FreeType, then it needs to
>> include it inside it's own bundle.
> Agreed. An end user getting the runtime, say from java.com, can not be
> required to install an optional component. They frankly would not want
> to go through the effort and would likely be confounded by the
> process, even with 'cookie cutter' instructions. I know that I would
> not want to explain that process to my mother-in-law :)
More information about the macosx-port-dev