OpenJDK build and libfreetype

[David Holmes]

On 26/10/2012 2:06 AM, Magnus Ihse Bursie wrote:
> Freetype is not used when building with closed sources, so it has not been finding itself, it has never been used. Still, it's weird that configure let you pass without a valid freetype path. What did configure print while checking freetype?

checking for FREETYPE2... yes

configure:16900: checking for FREETYPE2
configure:16907: $PKG_CONFIG --exists --print-errors "freetype2"
configure:16910: $? = 0
configure:16923: $PKG_CONFIG --exists --print-errors "freetype2"
configure:16926: $? = 0
configure:16961: result: yes

So it was looking to see if freetype2 is installed on the build machine 
(which it is) but nothing was actually setting the path.

I think this is fixed now anyway because latest build-infra does:

checking for FREETYPE2... yes
checking for FT_Init_FreeType in -lfreetype... no
configure: error: Could not find freetype2!

Though if we have to set the path the pkg check seems redundant.

Thanks,
David


> /Magnus
>
> 25 okt 2012 kl. 03:20 skrev David Holmes<david.holmes at oracle.com>:
>
>> On 24/10/2012 9:49 PM, Magnus Ihse Bursie wrote:
>>> On 2012-10-24 03:16, David Holmes wrote:
>>>> Probably a FAQ but I just tried to force an OpenJDK build of my forest
>>>> and it failed:
>>>>
>>>> /usr/bin/ld: cannot find -lfreetype
>>>>
>>>> what do I have to set to make this work?
>>>
>>> You have to specify --with-freetype to configure, pointing to your
>>> freetype installation.
>>
>> I don't normally so it is finding it itself for non-openjdk builds.
>>
>>> I'm not sure why a missing freetype wasn't caught by configure, though.
>>
>> Me neither. All I'm changing is whether it is an openjdk build or not.
>>
>> The good news is that --with-java-path fixed it for me.
>>
>> David
>>
>>> On the other hand, the freetype handling in configure is currently
>>> really crappy, so I'm not surprised. (I'm hoping I'll have enough time
>>> to fix that before I leave.)
>>>
>>> /Magnus