RFR: 8136556 - Add the ability to perform static builds of MacOSX x64 binaries
bob.vandette at oracle.com
Fri Oct 16 19:06:15 UTC 2015
> On Oct 16, 2015, at 1:01 PM, Naoto Sato <naoto.sato at oracle.com> wrote:
> Hi Bob, Alan,
> On 10/16/15 8:11 AM, Bob Vandette wrote:
>>> I've skimmed through the patches and the DEF_* macros look okay. The only one that doesn't look right is jawt.h/jawt.c. As jawt.h is shipped by the JDK then I think the include of jni_util.h needs to move from jawt.h to jawt.c.
>> Ok, I’ll take care of that.
>>> If I read the changes correctly then not loading the JavaRuntimeSupport.framework on Mac means the locale might not be right, is that correct? Brent might remember this issue as we've often pondered the implications of this disappearing in an Mac update.
>> The implementation falls back to the getPosixLocale function when the Framework doesn’t exist.
> In that case, the locale settings in the MacOSX's Settings will not be reflected in Java's default locale.
Unless we have the sources to the JavaRuntimeSupport, I see no way around this limitation.
Any attempt to load the shared library, causes the JavaRuntimeSupport framework to try to initialize itself.
The initialization fails since it can’t detect the presence of the Java runtime that’s trying to load it and a dialog
box asking to install Java appears.
I think we’re going to have to live with this limitation.
More information about the core-libs-dev