On Tue, 14 Apr 2026 09:33:39 GMT, Jaikiran Pai <[email protected]> wrote:
>> I guess your best bet would be to get a container with necessary bells and >> whistles, mount the JDK sources to a folder there, and issue a `make >> configure docs`. > > Hello James, > >> Any advice on how to build the javadoc without a full C++ development >> environment will be gratefully received. > > As long as you have `make` working against the JDK repo, you can do `make > docs-image` and that should generate the javadoc files under > `build/<xxx>/images/docs/` directory. nope - the configure (needed to run the make targets) script bails out - as I do not have any C++ development kit. I am also running inside WSL2 so using a Linux kernel 🤷 jnord@dev:/src/github/openjdk/jdk$ bash configure ... checking for docs-reference JDK... no, using interim javadoc for the docs-reference targets checking what source date to use... 1776165596, from 'current' (default) checking if we should build headless-only (no GUI)... disabled, default checking if linker should clean out unused code (linktime-gc)... disabled, default checking for graphviz dot... no, cannot generate full docs or man pages checking for pandoc... no, cannot generate full docs or man pages checking for --enable-full-docs... disabled, from default 'auto' checking for cacerts file... default checking for cacerts source... default checking for --enable-unlimited-crypto... enabled, default checking for jni library path... default configure: Using default toolchain microsoft (Microsoft Visual Studio) configure: error: Cannot locate a valid Visual Studio installation configure exiting with result code 1 `Linux dev 6.6.87.2-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Thu Jun 5 18:30:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux` ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30074#discussion_r3079057012
