diff --git a/.hgtags b/.hgtags index 58e232d224b..bb824527e83 100644 --- a/.hgtags +++ b/.hgtags @@ -456,3 +456,5 @@ b87d7b5d5dedc1185e5929470f945b7378cdb3ad jdk-10+27 a6e591e12f122768f675428e1e5a838fd0e9c7ec jdk-10+29 8fee80b92e65149f7414250fd5e34b6f35d417b4 jdk-10+30 e6278add9ff28fab70fe1cc4c1d65f7363dc9445 jdk-10+31 +a2008587c13fa05fa2dbfcb09fe987576fbedfd1 jdk-10+32 +bbd692ad4fa300ecca7939ffbe3b1d5e52a28cc6 jdk-10+33 diff --git a/doc/building.html b/doc/building.html index 357b0f5fb4b..bd4c1d80ddd 100644 --- a/doc/building.html +++ b/doc/building.html @@ -871,9 +871,9 @@ test-support/

When building for distribution, zipped is a good solution. Binaries built with internal is suitable for use by developers, since they facilitate debugging, but should be stripped before distributed to end users.

Autoconf Details

The configure script is based on the autoconf framework, but in some details deviate from a normal autoconf configure script.

-

The configure script in the top level directory of OpenJDK is just a thin wrapper that calls common/autoconf/configure. This in turn provides functionality that is not easily expressed in the normal Autoconf framework, and then calls into the core of the configure script, which is the common/autoconf/generated-configure.sh file.

+

The configure script in the top level directory of OpenJDK is just a thin wrapper that calls make/autoconf/configure. This in turn provides functionality that is not easily expressed in the normal Autoconf framework, and then calls into the core of the configure script, which is the make/autoconf/generated-configure.sh file.

As the name implies, this file is generated by Autoconf. It is checked in after regeneration, to alleviate the common user to have to install Autoconf.

-

The build system will detect if the Autoconf source files have changed, and will trigger a regeneration of common/autoconf/generated-configure.sh if needed. You can also manually request such an update by bash common/autoconf/autogen.sh.

+

The build system will detect if the Autoconf source files have changed, and will trigger a regeneration of make/autoconf/generated-configure.sh if needed. You can also manually request such an update by bash make/autoconf/autogen.sh.

If you make changes to the build system that requires a re-generation, note the following:

* *

Related Documentation

- *

+ * * For overviews, tutorials, examples, guides, and tool documentation, * please see: *