RFR: 8338768: Introduce runtime lookup to check for static builds [v2]
Magnus Ihse Bursie
ihse at openjdk.org
Mon Aug 26 09:39:04 UTC 2024
On Sun, 25 Aug 2024 14:57:22 GMT, Alan Bateman <alanb at openjdk.org> wrote:
> That is true for now but there 30-50 other places that will need attention once this effort is further along. Everywhere that deals with user editable configuration (conf tree) will change, as will everywhere that reads JDK internal files in the lib directory.
Well, yes and no. What you are talking about is the Hermetic Java project as a whole. This is about making the build smarter and more efficient at producing static libraries.
While static libraries are a sine qua non for Hermetic Java, it is also produced by other reasons. (For instance, the GraalVM and the Mobile Project). It is true that Hermetic Java was what actually got me to prioritize getting static builds to work properly, but the fact is that it has been a sore point for a long time, and the fact that we need to build all object files twice is actually putting a noticable effect on the Oracle CI system.
So please don't confuse the cleanup of static builds with the eventual goals of Hermetic Java. The runtime changes needed to read config files from a single binary will need to stand on it's own. The changes in this PR is good for us, regardless of however Hermetic Java proceeds.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/20666#issuecomment-2309780980
More information about the core-libs-dev
mailing list