javadoc and API docs
david.holmes at oracle.com
Mon Mar 26 05:53:07 PDT 2012
On 26/03/2012 10:43 PM, Alan Bateman wrote:
> On 26/03/2012 12:34, Jonathan Gibbons wrote:
>> Right now, in the current build, we use a "hybrid" javadoc to build
>> the API documentation, where "hybrid" means: latest sources, running
>> on bootstrap JDK.
>> Looking to the future, at least for Jigsaw, and now maybe for JSR 308,
>> we may need to run javadoc on the newly built JDK. Does anyone see any
>> problems with doing that?
>> -- Jon
> The cross-compile case, say to an embedded target, means the newly built
> JDK is not directly runnable although one could image skipping the
> javadoc in such a build.
> In the Jigsaw build then it already has to run tools such as jmod on the
> built JDK. For the cross-compile case it means doing two builds, one for
> the host platform, and then a second build for the target. When building
> for the target then the host JDK is specified via the JDK_HOST_PATH
> variable. If you are changing the generation of the API docs then you
> may need to have something similar.
To repeat what was said on the "build error" thread ...
More generally the boot JDK (aka JDK_HOST_PATH) run on the host has to
be the same version as the sources being cross-compiled. In the
non-jigsaw build we use HOST_CC, HOST_JAVA etc to run on the host using
the boot JDK (which is the linux-x86 build of the current sources). The
same would be needed for javadoc. That said we have no reason to build
More information about the build-dev