Linking to JavaRuntimeSupport framework

[Michael Papp]

> From: Scott Palmer <swpalmer at gmail.com>
> Subject: Re: Linking to JavaRuntimeSupport framework
> To: Gary Meyer <gary.meyer at apple.com>
> Cc: macosx-port-dev at openjdk.java.net
>
>
> On 2011-01-26, at 2:50 PM, Gary Meyer wrote:
>
> >
> > On Jan 26, 2011, at 11:39 AM, David Kocher wrote:
> >
> >> Thanks for the clarification. I was mixing things up.
> JavaRuntimeSupport.framework is indeed part of the public JavaVM.framework.
> Can you assure that this framework will be in the default install of
> subsequent major OS X releases (10.7 and onward)? The Java deprecation
> notice never made it clear to me, what parts will be optional installs. I
> would assume that only  /System/Library/Java/JavaVirtualMachines/* falls
> into this category then.
> >>
> >> -
> >> David
> >
> > You seem to be implying that you should be able to build Java without
> having Java installed.  That most certainly is not true.  You must have Java
> installed in order to build Java, thus you will have JavaRuntimeSupport
> whenever you have Java installed.  Whether it is there or not when you don't
> have Java installed shouldn't (and doesn't) matter.
> > Gary.
>
> I think the suggestion is that JavaRuntimeSupport is not part of OpenJDK
> (right?) and therefore how do you get it installed when Apple stops shipping
> it's own Java runtime.
>
> Scott
>
>
Gary - I don't think the question is entirely about building.  If you are
linking against JavaRuntimeSupport.framework, you will of course need it on
your build machine (along with Java, etc.).  The issue here is whether the
framework will continue to be shipped by Apple when you deploy a JRE based
on OpenJDK Mac OS X.  In other words, you can build the entire JRE from open
source *except* for this framework, which means either you need to be able
to distribute this (presumably proprietary Apple) framework with your JDK,
or Apple needs to insure that it is available on current/future OS releases.

Mike