New official README-builds.html

[Phil Race]

There was at least one specific bad version of freetype that worked 
apparently
  to Linux users but not to people on an O/S with fonts with embedded 
bitmaps.

But just like you aren't setting up your envt right such that it can't 
find the .so.
If the build can't infer the lib location from the include location you 
will need to supply both,

-phil.


On 3/4/13 5:57 PM, Kelly O'Hair wrote:
> freetype 2.3 or newer is what the docs say, but I have heard that 2.4 might not work.
> I think we use 2.3.4 inside Oracle.
>
> -kto
>
> On Mar 4, 2013, at 12:21 PM, Akhil Arora wrote:
>
>> Thanks - I put the boot jdk in /d/jdk7 and added --with-num-cores=1, which made the hang go away and the build went further.
>>
>> Now I'm getting unresolved symbol errors for freetype when trying to build fontmanager.lib, I downloaded freetype from http://www.gtk.org/download/win32.php and used --with-freetype=/d/freetype-2.4.2-1 in configure -
>>
>> ## Starting jdk
>>    Creating library d:/nashorn/build/windows-x86_64-normal-server-release/jdk/objs/libfontmanager/fontmanager.lib and object d:/nashorn/
>> build/windows-x86_64-normal-server-release/jdk/objs/libfontmanager/fontmanager.exp
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Done_FreeType referenced in function freeNativeResources
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Done_Face referenced in function freeNativeResources
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Open_Face referenced in function Java_sun_font_FreetypeFontScaler_initNativeScaler
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_New_Memory_Face referenced in function Java_sun_font_FreetypeFontScaler_initNativeScaler
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Init_FreeType referenced in function Java_sun_font_FreetypeFontScaler_initNativeScaler
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Activate_Size referenced in function setupFTContext
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Set_Char_Size referenced in function setupFTContext
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Set_Transform referenced in function setupFTContext
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_MulFix referenced in function Java_sun_font_FreetypeFontScaler_getFontMetricsNative
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Render_Glyph referenced in function Java_sun_font_FreetypeFontScaler_getGlyphImageNative
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_GlyphSlot_Oblique referenced in function Java_sun_font_FreetypeFontScaler_getGlyphImageNative
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_GlyphSlot_Embolden referenced in function Java_sun_font_FreetypeFontScaler_getGlyphImageNative
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Load_Glyph referenced in function Java_sun_font_FreetypeFontScaler_getGlyphImageNative
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Get_Char_Index referenced in function Java_sun_font_FreetypeFontScaler_getGlyphImageNative
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Outline_Translate referenced in function getFTOutline
>> freetypeScaler.obj : error LNK2019: unresolved external symbol FT_Outline_Get_BBox referenced in function Java_sun_font_FreetypeFontScaler_getGlyphOutlineBoundsNative
>> d:/nashorn/build/windows-x86_64-normal-server-release/jdk/bin/fontmanager.dll : fatal error LNK1120: 16 unresolved externals
>> make[2]: *** [/d/nashorn/build/windows-x86_64-normal-server-release/jdk/bin/fontmanager.dll] Error 96
>> make[1]: *** [libs-only] Error 2
>> make: *** [jdk-only] Error 2
>>
>> On 3/4/2013 8:02 AM, Kelly O'Hair wrote:
>>> Using any paths with blanks in them is a risk, I would use a boot jdk that has a path without spaces.
>>>
>>> I also never use the java installed by any automated process, or system update mechanism because
>>> your boot jdk could change on you at any time.
>>> I get the jdk image needed, e.g. 7u7 or whatever, put it in a simple short directory, and keep it safe.
>>>
>>> Predictable build results is a matter of minimizing the variability, so you really never want to use
>>> things that are constantly changing on you. Some things you cannot control, but some you can.
>>>
>>> I am not a MSYS user, but I have heard there were some stability issues, so step one might be to use
>>>   --with-num-cores=1 to start, until you get it working.
>>>
>>> -kto
>>>
>>> On Mar 1, 2013, at 11:20 AM, Akhil Arora wrote:
>>>
>>>> Hi Kelly
>>>>
>>>> I can build without any problems on linux. I'm trying to follow the instructions in the new README to build on Windows 7 with MSYS, but my build gets stuck, the output on the console with LOG=debug is
>>>>
>>>> make[1]: Entering directory `/d/nashorn/langtools/makefiles'
>>>> /bin/mkdir -p /d/nashorn/build/windows-x86_64-normal-server-release/langtools/btclasses/bootstrap/com/sun/tools/doclets/internal/toolkit/resources
>>>> /bin/mkdir -p /d/nashorn/build/windows-x86_64-normal-server-release/langtools/btclasses/bootstrap/com/sun/tools/doclets/internal/toolkit/resources
>>>>
>>>> I checked, this dir has been created, but the build gets stuck at this step for a long time. The only process running (in Task Manager) at this time is make. The flags I used for configure are -
>>>>
>>>> $ bash ./configure --prefix=/d --disable-headful -with-freetype=/d/freetype-i586 --with-boot-jdk=/d/Program\ Files/Java/jdk1.7.0 --with-num-cores=2 --with-memory-size=2048 --with-boot-jdk-jvmargs=-Xmx2g
>>>>
>>>> Any ideas?
>>>>
>>>> On 3/1/2013 9:18 AM, Kelly O'Hair wrote:
>>>>> Please do not 'reply all', send concerns or issues to just the build-dev or build-infra-dev aliases.
>>>>>
>>>>> The very latest README-builds.html file is:
>>>>>     http://hg.openjdk.java.net/jdk8/jdk8/raw-file/tip/README-builds.html
>>>>>
>>>>> This documents the new build makefiles only.
>>>>> As with all documents of this type, it will always be a work in progress.
>>>>>
>>>>> -kto
>>>>>