problem with libfontmanager in jdk 1.7.0u

[Phil Race]

1) Building freetype should be as easy as
* Download
* ./configure
* ./make

2) Making it available to the build should be as easy as
ALT_FREETYPE_HEADER_PATH=<your install>
ALT_FREETYPE_LIB_PATH=<your install>


But I find there are a couple of wrinkles.

1. Freetype builds in /usr/local/lib as the path to find it at runtime 
using some OS X linker behaviour.
    It needs to be built to say to use a relative path else its useless.
   There's hopefully some easy configure option for this but I don't 
know what it is.

This is even a build time issue because the infamous freetypecheck 
program needs to link against it.

2. Should be somewhat easier to deal with but from what I can tell, on OSX,
the build code seems to insist on setting
USING_SYSTEM_FT_LIB=true
which amongst other things means  "no need to copy freetype into the JRE,
expect to use the system one".
In the presence of the "ALT_" paths that really should default to false, 
unless
explicitly told otherwise.

-phil.

On 2/20/2012 4:12 PM, Mike Swingler wrote:
> On Feb 20, 2012, at 3:43 PM, Henri Gomez wrote:
>
>>> The ideal solution is include instructions for obtaining, building, and integrating FreeType into the JDK build on<https://wikis.oracle.com/display/OpenJDK/Mac+OS+X+Port>.
>>>
>>> Does anyone have a simple step-by-step instructions for how to pick the right release, building a minimal library required by OpenJDK, and then pointing the Mac JDK build at it?
>> Do you means we should include freetype lib into OpenJDK to avoid
>> brutal change in future OSX release ?
>> Did there is others libraries which may have to be embedded also in the future ?
>
> Yes, a .jdk or .jre bundle needs to include it's of FreeType library, since FreeType on Mac OS X is delivered via the X11 package, which has always been optionally installable (even though it has been a checked by default option).
>
> I would advocate for circumventing the whole problem by not relying of FreeType, but if that's not possible, bundling is the only other obvious option. If bundling is necessary, the build instructions need to document how to obtain, build, and include the library into the final build JDK product.
>
> Regards,
> Mike Swingler
> Apple Inc.
>