RFR: 8351493: Revert build changes that are no longer needed [v2]

[Jiangli Zhou]

On Thu, 20 Mar 2025 22:17:29 GMT, Magnus Ihse Bursie <ihse at openjdk.org> wrote:

> I don't really see how this differs from the dynamic case. The distributor building the JDK must decide whether to use the system libraries (typically done by Linux distributions, since they have control over such things), or bundle it (most other). The same goes for when building a static library. Even if we allow some kind of "mix and match" with jlink, there needs to be some kind of limit on how much a single version of the JDK can provide for. In one extreme, mixing different address sizes or CPU architectures is not possible, and will never be. On the other hand, libjsig has been provided as an optional library. So somewhere between there will libharfbuzz need to fall. My instinct is that it is not like libjsig but rather like the OS; that is, for a specific instance of the JDK a distributor builds, they decide not only OS and CPU, but also if libraries like harfbuzz should be included or not, both for static and dynamic.

Thanks for the reasoning with dynamic case. It does make sense to treat libharfbuzz and other bundled libs on static the same as on dynamic JDK.

-------------

PR Comment: https://git.openjdk.org/leyden/pull/47#issuecomment-2741824171