Use of OPENWIN_HOME on linux
David Holmes
David.Holmes at oracle.com
Thu Oct 21 08:55:16 UTC 2010
Thanks Chris. I had just this minute come to the realization that the
JDK6 code is the code that changed, while JDK7 has the original code.
Those CRs are somewhat lacking in detail, but cross-compilation is
exactly why this needs to be settable.
I'm working on the SE-Embedded merge with JDK7, so I can make the change
as part of that work, to support cross-compilation. Just wanted to get a
better understanding of why things were the way they are before I
started making changes.
Cheers,
David
Chris Hegarty said the following on 10/21/10 18:46:
> David,
>
> Looking at the history of Defs-linux.gmk you can see that
> (ALT_)OPENWIN_HOME was added for CR 2154143, in JDK6u10. This CR is also
> marked as fixed in JDK7 b65 ( my guess would be as part of the forward
> port of the client 6u10 stuff ). I'm not sure why the ALT_OPENWIN_HOME
> support was never forward ported. I've cc'ed the relevant RE's, they
> should be able to give a better reasoning.
>
> -Chris.
>
> On 21/10/2010 05:40, David Holmes wrote:
>> It used to be in JDK6 that you could use ALT_OPENWIN_HOME to override
>> the default OPENWIN_HOME settings in the makefiles for the j2se
>> workspace. But now in JDK7 this has gone and the value is hardwired in
>> Defs-linux.gmk:
>>
>> override OPENWIN_HOME =/usr/X11R6/
>>
>> Can someone tell me why this change was made? It seems to go against the
>> normal policy of using the ALT_* variables to customize settings.
>>
>> This value needs to be overridden externally when doing
>> cross-compilation.
>>
>> Thanks,
>> David
More information about the core-libs-dev
mailing list