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

List:       openjdk-build-dev
Subject:    Fwd: JDK build on Mountain Lion
From:       artem.ananiev () oracle ! com (Artem Ananiev)
Date:       2012-07-30 8:43:17
Message-ID: 50164925.7000605 () oracle ! com
[Download RAW message or body]


On 7/27/2012 10:27 PM, Phil Race wrote:
> I don't know why we build xawt on OS X - at least by default.
> We don't use X11 for UI in our JDK on Mac and I'm 99% sure its not
> getting tested.
> Building the XAWT toolkit on OS X perhaps should be an optional selection

Yes, we plan to purge XAWT from OS X in JDK8.

Thanks,

Artem

> -phil.
>
> On 7/27/2012 10:48 AM, Kelly O'Hair wrote:
>>
>> Some interesting information on anyone trying to build OpenJDK on
>> Mountain Lion... 10.8 I assume.
>>
>> -kto
>>
>> Begin forwarded message:
>>
>>> From: Naoto Sato<naoto.sato at oracle.com>
>>> Subject: JDK build on Mountain Lion
>>> Date: July 27, 2012 9:52:02 AM PDT
>>> To: Kelly O'Hair<kelly.ohair at oracle.com>
>>> Cc: JAVA_I18N_WW_grp at oracle.com
>>>
>>> Hi Kelly,
>>>
>>> This is just fyi. I just upgraded my MBP to Mountain Lion, and tried
>>> to build JDK8 on it. Obviously, Apple removed all the X11 stuff from
>>> XCode by default and initially it failed somewhere building AWT.
>>>
>>> X11 stuff has been installed when I ran some X11 app (like Java
>>> runtime, Apple now installs a stub X11 server which just pops up a
>>> message box that urges the user to install 3rd party X11 stuff - XQuarz)
>>>
>>> There is another hiccup with it. That is, the default include search
>>> path for the C compiler. Now that the X11 stuff is not included in
>>> Mountain Lion, /usr/include/X11 is no longer searched. I had to set
>>> it with "CPATH" environment variable. Maybe this is something that
>>> JDK build script could help.
>>>
>>> Naoto
>

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